What is the challenge?
Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description.
What is the impact?
This leads to significant data loss — important contextual information, formatting, or...
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
Russell Roach
over 5 years ago
in Jira
3
Future consideration
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest
almost 7 years ago
in Jira
6
Future consideration
Ability to update Jira Affects Versions field from Aha via integration
What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner
over 1 year ago
in Jira
1
Future consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
over 10 years ago
in Jira
17
Future consideration
What is the challenge?
When integrations are out of sync with AHA and JIRA where JIRA holds the source information.
(1) Delete records in Aha and re-import. This creates issues for any integrations that were set-up in Aha
(2) Use Update Records...
Guest
about 2 months ago
in Jira
0
Future consideration
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
almost 3 years ago
in Jira
2
Future consideration
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira
almost 2 years ago
in Jira
2
Future consideration
Ability to map custom Initiative fields in Jira integrations
What is the challenge?
Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration.
What is the impact?
Unable to pass this information over to Jira
Describe your ...
Stephanie Lechner
4 months ago
in Jira
0
Future consideration