ADD A NEW IDEA

Jira

Showing 261

Ability to aggreate work done value from both feature and requirements

Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when: 1. there is a time log in JIRA on epic (synced to feature) 2. there is a time log...
Daniel Pokrývka about 5 years ago in Jira 2 Future consideration

Calculate Epic Completion Based on JIRA Epic Completion

The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
Rachelle S over 1 year ago in Jira 0 Already exists

Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited

In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Kevin Burges about 7 years ago in Jira 0 Unlikely to implement

Send events before deletion

We currently sync a field in Aha! to Jira when a record is created. We’d like to clear that field if the record is deleted from Aha! I’m looking to send an update to the field or set an event trigger to make a note that the field value has changed.
Yancey Larochelle-Williams over 3 years ago in Jira 0 Future consideration

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated Currently, I have three JIRA projects integrated to a single AHA product: LCI TEAM METHD UXH Currently, these three projects show up as Send to JIRA Send to JIRA Sen...
Guest over 7 years ago in Jira 5 Already exists

Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status

We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
Guest over 3 years ago in Jira 1 Future consideration

Improved error message on incorrect JIRA record type link

Using the JIRA 2.0 integration, if you try to link to an existing record type that is not mapped in the integration config, the error message is very unhelpful. It just says "system error - contact Aha support if this persists" (or something like ...
Mat Wood over 5 years ago in Jira 0 Future consideration

Ability to search on the Jira Key

We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
Guest almost 6 years ago in Jira 1 Already exists

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest almost 8 years ago in Jira 0 Already exists

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Guest almost 4 years ago in Jira 3 Already exists