Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 273 of 9771

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

Automatically update roll-up release name in integrations

Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
Nico Arias-Gonzalez almost 2 years ago in Integrations / Jira 0 Future consideration

Show comments added in JIRA as part of a state transition.

Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA. This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi over 6 years ago in Jira 2 Future consideration

Add Product Name to JIRA Integration

The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin over 6 years ago in Jira 0 Future consideration

Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
Anh Truong over 4 years ago in Jira 1 Future consideration

Jira integration - pre filter based on tag/field

Often there are items on a roadmap that do not require Engineering work. However when a release is sent to Jira (or over dev system) all the items under that release are also sent. This means that the down stream system can become full of items in...
Ann L almost 4 years ago in Jira 0 Future consideration

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller almost 4 years ago in Jira 0 Future consideration

Include JIRA records in linked records

We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
Guest almost 9 years ago in Jira 2 Unlikely to implement

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 t...
Matthew Monahan almost 6 years ago in Jira 0 Future consideration

Set Rank order from Jira to Aha!

When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
Guest almost 6 years ago in Jira 1 Future consideration