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 6 years ago
in Jira
2
Future consideration
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 7 years ago
in Jira
0
Future consideration
Ability to map custom Initiative fields in Jira integrations
What is the challenge?
Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration.
What is the impact?
Unable to pass this information over to Jira
Describe your ...
Stephanie Lechner
about 2 months ago
in Jira
0
Future consideration
Add an option for JIRA integration to re-import all stories under an epic
What is the challenge?
Sometimes we links epics after they are created. In this case stories aren't linked automatically. That means we need to do an extra step to import the stories
What is the impact?
Error prone and aha doesn't reflect ...
David G
6 months ago
in Jira
0
Future consideration
Ability to import JIRA labels to Aha Requirement Tags
What is the challenge? Unable to import JIRA labels to Aha Requirement Tags What is the impact? DSG tracks in JIRA Stories which business silo owns the work with Tags and tags if the work is carry over from a previous springs. DSG needs those tags...
Jira & Aha Integration - Ability to refresh Aha records making either Jira or Aha the dominant source
What is the challenge? We would like to have the ability to refresh the Aha record based on Jira updates. Currently, inside the integrated Aha ticket, users can only resend the updates they made in Aha into Jira, but not the other way around. We w...
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
Stephanie Lechner
about 1 year ago
in Jira
0
Future consideration
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
over 1 year 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
over 1 year ago
in Integrations / Jira
0
Future consideration
Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder
about 2 years ago
in Jira
1
Future consideration