Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 260

Epic progress doesn't update when it has children in different projects

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira 10 months ago in Jira 0 Future consideration

Jira sprint dates as feature end dates

With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe over 5 years ago in Jira 4 Future consideration

Ability to sync Jira's "Team" bidirectionally

What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
Michael Tucker 2 months ago in Jira 0 Planning to implement

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black about 2 years ago in Jira 1 Future consideration

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest over 7 years ago in Jira 5 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer almost 7 years ago in Dependencies / Jira 3 Future consideration

Ability to update Jira Affects Versions field from Aha via integration

What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner 2 months ago in Jira 0 Future consideration

Map detailed estimates by initiative in Jira integration

What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus 2 months ago in Jira 0 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer over 9 years ago in Jira 12 Planning to implement

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox almost 4 years ago in Jira 0 Future consideration