Add Product Prefix field as a choice in the JIRA integration
We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
Guest
over 5 years ago
in Jira
0
Future consideration
Allow for "approve incoming changes" in Jira integration
There is currently an option to approve outgoing changes or incoming records, but not incoming changes.
The current options are:
- Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to...
Guest
over 5 years ago
in Jira
0
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 2 years ago
in Jira
0
Future consideration
Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest
over 2 years ago
in Jira
2
Future consideration
The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden
over 2 years ago
in Jira
0
Future consideration
Merge Custom Fields into One Field when they are carried over from Idea to Feature
At idea stage you capture information about the idea in multiple fields, when you promote this to a feature if this information was merged into one 'Body' field, then I would save time not having to copy and paste those fields into one field.
...
Guest
over 5 years ago
in Jira
0
Unlikely to implement
To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.
Danielle A
over 2 years ago
in Jira
0
Future consideration
This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
Ryan Schultz
over 8 years ago
in Jira
0
Already exists
On the Aha! Integration Updates screen for an Aha! to/from Jira Integration, I would like to see which releases and the status of what each of the items are for integration. Being offered these filters would allow me to select that before importin...
Guest
over 5 years ago
in Jira
1
Unlikely to implement