Skip to Main Content
ADD A NEW IDEA

Jira

Showing 87

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
Danny Archer over 9 years ago in Jira 4 Shipped

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...
Emilie Takeda almost 9 years ago in Jira 7 Shipped

Support for Jira Embedded Images

Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets...
Guest about 7 years ago in Jira 3 Shipped

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...
Danny Archer over 6 years ago in Integrations / Jira 8 Shipped

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...
Kelly Sebes about 6 years ago in Jira 3 Shipped

Support JIRA issues being unassigned

If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Danny Archer over 8 years ago in Jira 2 Shipped

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...
Matt Case over 8 years ago in Jira 3 Shipped

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...
Guest over 8 years ago in Jira 3 Shipped

Sync "Sprint" Field from JIRA

Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...
Guest over 6 years ago in Jira 2 Shipped

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 ...
Guest over 9 years ago in Jira 1 Shipped