Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 265

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest almost 6 years ago in Jira 2 Future consideration

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
Guest almost 10 years ago in Comments / Notifications / Jira 1 Unlikely to implement

Automatically Update Records Converted in Jira

What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
Guest 6 months ago in Jira 0 Future consideration

Don't Allow Jira Integration to Fail Based on One Field

What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...
Guest 6 months ago in Jira 0 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest over 7 years ago in Jira 3 Future consideration

Support mapping tags to JIRA multicheckboxes

Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
Austin Merritt about 6 years ago in Jira 0 Future consideration

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 8 years ago in Jira 11 Already exists

Map one Aha release to several Jira projects

We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the...
Guest about 6 years ago in Jira 0 Future consideration

Automatically send feature(s) to integrated system

As a product manager I want to have a feature I just created be automatically created in my integrated system, such as Jira. Adding a check box in the integration configuration for "Automatically send issue to integrated system" would be an easy w...
Guest over 6 years ago in Jira 5 Unlikely to implement

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest over 9 years ago in Jira 9 Unlikely to implement