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
over 5 years ago
in Jira
2
Future consideration
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
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
almost 2 years ago
in Jira
0
Already exists
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
almost 4 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...
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
almost 4 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
almost 6 years ago
in Jira
0
Future consideration
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).
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...
Feature Email update notification to include link direct to Jira record
From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
Scott C
about 6 years ago
in Jira
0
Future consideration