What is the challenge? Companies that use both Jira and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requirement...
Kelly Sebes
8 months ago
in Ideas / Jira
6
Shipped
Allow switching between integration templates if they are integrated with the same project
What is the challenge? As part of a migration, we are planning to change existing integrations and switch from using "Template A" to "Template B". The challenge is that "Template B" is not available for selection unless it is integrated with the s...
Dale Potter
4 months ago
in Integrations
2
Shipped
Do not show an update to the record description in History when sending a record to an integration
What is the challenge? When you send a record to an integration, the history incorrectly indicates that there was an update to the description. What is the impact? This can cause confusion about what changes were actually made. It also impacts tho...
Emily Yankush
about 2 months ago
in Integrations
1
Shipped
Update progress and link to integration on background jobs
What is the challenge? When I run the Update records utility for many integrations, the background jobs page does not show an updated progress for each job. Also, if the job fails there is no link back to the integration so I can quickly find and ...
Justin Waldorf
6 months ago
in Integrations
1
Shipped
Improve Component mapping in Jira and updated error handling
What is the challenge? When mapping Components in Jira to a predefined choice custom field in Jira, you are not given the option to map the values. If there is a failure in the import due to this field, no record or error information is displayed....
Move epic/feature to default release when integrations unlink the release
What is the challenge? When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! r...
Jeanette Resnikoff
3 months ago
in Integrations
1
Shipped
Sync record's workspace, goal, initiative, epic, and release (name and link) to integrations
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker
over 6 years ago
in Jira
14
Shipped
Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT
We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris
over 8 years ago
in Jira
17
Shipped