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 6 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
about 6 years ago
in Jira
0
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 6 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 7 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
almost 7 years ago
in Jira
0
Future consideration
Attachments linked to Note custom fields should be supported in Integrations 2.0
The note custom field allows for documents to be attached. However, when "attachments" are synchronized between Aha! and the development system, only attachments linked to the Description field are sent over. It would be ideal if the documents att...
Guest
over 7 years 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
over 7 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
over 7 years ago
in Jira
2
Future consideration
Ability to map editable choice lists in Aha! with the Jira Team field and support bi-directional sync
What is the challenge?
Bi-directional sync of the Jira team field is only supported for some Aha! custom fields
What is the impact?
Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...
Deepti Pradeep
about 1 month ago
in Jira
1
Future consideration
Add "Idea votes" and "Account" to the list of idea fields that can be mapped to Jira
What is the challenge? We cannot see information on the account that an idea came from or how many votes an idea has in Jira What is the impact? Product Manager's time is wasted going back and forth to remember where an idea came from or to pass t...