In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...
Mat Buehler
over 1 year ago
in Jira
0
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
over 5 years ago
in Jira
0
Future consideration
To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...
Alfred S
over 2 years ago
in Jira
0
Future consideration
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes me...
Michael Clinton
over 8 years ago
in Jira
1
Future consideration
Ability to update a file attachment of a feature and update in the linked record of JIRA as well
Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda
almost 7 years ago
in Jira
1
Future consideration
New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration
There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin
over 2 years ago
in Jira
0
Future consideration
When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
Roger Octobre
about 4 years ago
in Jira
0
Future consideration
When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following:
Created in Jira by Matthew Monahan (****@****.com)
When I dig into the values in t...
Matthew Monahan
almost 5 years ago
in Jira
0
Future consideration
Who would benefit? Developers What impact would it make? Better requirements How should it work? Excel transfer to Jira because Jira does not support merged cells
Guest
10 months ago
in Jira
1
Unlikely to implement
Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong
over 2 years ago
in Jira
0
Future consideration