Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 265 of 9040

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

Improving handling when Jira users change issue type across record hierarchy

Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
Stephanie Lechner 12 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 about 9 years ago in Jira 12 Likely 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 over 3 years ago in Jira 0 Future consideration

If comment is deleted in Jira, add a tag <Deleted> to Aha to ensure users are aware of the change (& Vice versa)

What is the challenge? currently, comments that are deleted on one platform, do not get deleted on the other platform (& Vice Versa) What is the impact? Users who work dedicatedly on Aha (like Top Management) will continue to view out-dated co...
Maria V 3 months ago in Features / Jira 0 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush over 1 year ago in Jira 0 Future consideration

Excel Documents Not Sending to Jira Custom fields

Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
Guest 9 months ago in Jira 0 Future consideration

Ability to import child records when connecting to an existing record in Jira

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
Nerissa Muijs 6 months ago in Jira 0 Future consideration

Update JIRA integration when feature ranking changes in Aha

I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely c...
Guest over 5 years ago in Jira 6 Unlikely to implement

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black about 2 years ago in Jira 1 Future consideration