ADD A NEW IDEA

Jira

Showing 257

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 7 months ago in Jira 0 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest over 8 years ago in Jira 1 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 about 5 years ago in Jira 0 Future consideration

Copy integration mappings for records at the same hierarchy level

When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush about 1 year ago in Jira 0 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 1 year ago in Jira 0 Future consideration

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 8 years ago in Jira 2 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet over 5 years ago in Jira 1 Future consideration

JIRA Integration - Allow Changing Board

We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
Jonathan Shaw about 1 year ago in Jira 0 Future consideration

Excel Transfer to Jira

Who would benefit? Developers What impact would it make? Better requirements How should it work? Excel transfer to Jira because Jira does not support merged cells
Guest 7 months ago in Jira 1 Unlikely to implement

Send release phases to JIRA as proposed sprints

We would like to have a means to integrate Aha! release phases with JIRA sprints, as features included in phases are sent to JIRA.
Donna Sawyer almost 8 years ago in Jira 3 Unlikely to implement