Skip to Main Content
ADD A NEW IDEA

Jira

Showing 250

Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt

We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
Guest over 4 years ago in Jira 0 Future consideration

Better display of user info from Jira integration

When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following: Created in Jira by Matthew Monahan (****@****.com) When I dig into the values in...
Matthew Monahan over 4 years ago in Jira 0 Future consideration

Capability to tag JIRA users

As a user with an integration with JIRA, I want the ability to @ users in my feature, requirement, or comments in Aha and the @ will sync to the JIRA users available so they can receive a JIRA notification. Our dev team does not use Aha notificati...
Guest about 6 years ago in Comments / Notifications / Jira 0 Future consideration

JIRA Integration - allow bidirectional mapping of the "time frame" field

for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
Alan Valentine about 6 years ago in Jira 1 Future consideration

JIRA integration Import of only linked epics

When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
Guest over 4 years ago in Jira 0 Future consideration

Integration with JIRA needs better Error handling support

Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
Guest over 4 years ago in Jira 1 Future consideration

Link user stories (requirements) in JIRA when under the same epic (feature)

We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
Elizabeth Karam over 6 years ago in Jira 2 Future consideration

Allow "Predefined choice list" to select multiple items

Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
Guest about 8 years ago in Jira 0 Unlikely to implement

Ability to aggreate work done value from both feature and requirements

Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when: 1. there is a time log in JIRA on epic (synced to feature) 2. there is a time l...
Daniel Pokrývka almost 5 years ago in Jira 2 Future consideration

History of items created via integration

In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them. A modal notification like you currently use would work at a one-by-one level. If that makes sense. Even better would be a tab in ...
Max Cascone over 6 years ago in Jira 1 Future consideration