Often there are items on a roadmap that do not require Engineering work. However when a release is sent to Jira (or over dev system) all the items under that release are also sent. This means that the down stream system can become full of items in...
Ann L
almost 3 years ago
in Jira
0
Future consideration
Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings
We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...
Leanne Miller
over 4 years ago
in Jira
0
Future consideration
Integration with JIRA needs better Error handling support
Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
Guest
about 5 years ago
in Jira
1
Future consideration
Teach aha custom fields to auto-update its list of values based on JIRA custom fields
Dear aha, we have custom fields in JIRA, that we would like to keep in sync with mapped custom fields in AHA. Good example is a list "Country". We have that as global jira custom field with specific value list enabled per jira project. Whenever a ...
Daniel Pokrývka
over 5 years ago
in Jira
0
Future consideration
For Jira integration, enable ability to prevent releases being automatically created in Jira (and/or enable this for releases in parking lot)
Right now we have an integration set up between Jira and Aha (which is extremely useful). However, whenever a feature in Aha that's linked to an issue in Jira has its release updated (e.g. moved from "v1.12.0" to "Backlog"), if the release to whic...
Guest
almost 6 years ago
in Jira
0
Future consideration
Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date). U...
Guest
about 6 years ago
in Jira
0
Future consideration
Allow parking lot features and releases to not be sent to Jira
I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain
over 6 years ago
in Jira
1
Already exists
JIRA Integration - allow bidirectional mapping of the "time frame" field
for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
Alan Valentine
over 6 years ago
in Jira
1
Future consideration
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
Elizabeth Karam
almost 7 years ago
in Jira
2
Future consideration