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
over 1 year ago
in Jira
1
Future consideration
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
about 7 years ago
in Jira
1
Future consideration
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
Daniel Hirschberg
over 5 years ago
in Jira
0
Future consideration
Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt
We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
Guest
over 5 years ago
in Jira
0
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
about 7 years ago
in Jira
2
Future consideration
When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
Guest
over 5 years ago
in Jira
0
Future consideration
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
Max Cascone
over 7 years ago
in Jira
1
Future consideration
Ability to map Jira Web Links with Aha! URL at Integration
Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
Tej Namala
over 3 years ago
in Jira
0
Future consideration
Allow Jira Integration to synchronize External Release Dates
In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.
Guest
almost 2 years ago
in Jira
0
Future consideration
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