Jira
Sort by:
Popular
Status:
Shipped
Showing 102
32
VOTE
Integrations 2.0: Support importing unmapped issue types
In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types.
This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha!
This is important, without this we have no way t...
8
Shipped
29
VOTE
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
3
Shipped
29
VOTE
29
VOTE
Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects
The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...
3
Shipped
26
VOTE
Scorecard integration with JIRA business value
It's helpful for the scrum teams to not only see the Aha rank but also the business value associated with the scorecard. Integrating scorecard with JIRA Business Value is beneficial to members of the teams as well as reporting on the business valu...
3
Shipped
25
VOTE
25
VOTE
Improved automatic pull of items from Jira to ensure strategic relevance of Aha!
As a product manager with an engineering team that uses Jira, I understand and appreciate that Aha aims to remove the temptation for anyone to "sneak" tasks into Jira rather than through the PM and Aha!. The reality, though, is that agile sprints ...
1
Shipped
24
VOTE
Turn off 2-way synch for specific custom fields sent to Jira
Up until recently, custom field data was sent one-way Aha to Jira.
For certain fields, we prefer the data sent one-way. We want to be able to send information such as business goals so that people using Jira can understand more about what's trying...
0
Shipped
21
VOTE
Guide users to reload configuration when missing field in mappings
When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
0
Shipped
21
VOTE
Provide ability to map Created by user to Reporter field in the JIRA integration
When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...
5
Shipped
© 2025 Aha! Labs Inc.•All rights reserved