Add a tag to requirements, and sync it with jira labels
Why is it useful?
Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened.
Sometimes one team works on a...
Currently you are able to send features to Trello from Aha and their status will be updated as they are moved in Trello. However comments and attachments that are added to Trello cards/features do not move to Aha. Enabling this feature would allow...
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...
For successful product management and development, User Stories and Acceptance Criteria are key. We want our Product Owners defining not only the user story (requirement) but also the associated acceptance criteria within Aha!. This information wo...
We would love to allow our users to login with Google. We keep some important things in here and for the price we pay we treat it like an enterprise tool. I get a lot of flack for not being able to roll permissions into a identity management strat...
JIRA Import multiple issue types as requirements mapped to parent feature
As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
Aha! integration with should create a hyperlink record in TFS to link back to the Aha! item
Aha! integration with TFS should create a hyperlink in the TFS item when the Send to Team Foundation Server action is selected and a new TFS item is created. Additionally, an action that sends a link record to TFS would be helpful if the link is l...
Need to "Link with existing issue in JIRA" at requirement level
We have JIRA and Aha today and the tools are integrated as follows:
Aha feature - JIRA Epic
Aha requirement - JIRA story
NA - JIRA sub-task
For some reasons, I had to delete the integration with JIRA for a specific product line...