Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 270

Add better error handling for 'unhandled error exceptions'

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest almost 2 years ago in Jira 0 Future consideration

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest over 5 years ago in Account settings / Jira 1 Future consideration

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham about 6 years ago in Jira 2 Unlikely to implement

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...
Guest over 9 years ago in Jira 2 Future consideration

Allow Jira Epics to Integrate

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest over 2 years ago in Jira 0 Future consideration

Automatically create/update Notification Groups based on location hierarchy

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...
Guest about 3 years ago in Jira 0 Future consideration

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest almost 6 years ago in Jira 0 Future consideration

Aha Jira Integration mapping need to include the new Jira Object Capability

What is the challenge? Could not use the new Jira object in the mappings What is the impact? Teams want to group similar Epics in capability. without this, we can group them for tracking Describe your idea We already have Aha Integration to Jira i...
Guest 8 months ago in Jira 0 Future consideration

When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
Guest over 9 years ago in Ideas / Jira 4 Unlikely to implement

Deleting a feature or requirement should delete the linked Jira issue(s)

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
Guest over 10 years ago in Jira 11 Will not implement