Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox
over 3 years ago
in Jira
0
Future consideration
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush
over 1 year ago
in Jira
0
Future consideration
If comment is deleted in Jira, add a tag <Deleted> to Aha to ensure users are aware of the change (& Vice versa)
What is the challenge? currently, comments that are deleted on one platform, do not get deleted on the other platform (& Vice Versa) What is the impact? Users who work dedicatedly on Aha (like Top Management) will continue to view out-dated co...
Maria V
3 months ago
in Features / Jira
0
Future consideration
Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
Guest
10 months ago
in Jira
0
Future consideration
Update JIRA integration when feature ranking changes in Aha
I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely c...
Guest
over 5 years ago
in Jira
6
Unlikely to implement
When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black
about 2 years ago
in Jira
1
Future consideration
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black
about 2 years ago
in Jira
0
Future consideration
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
Nerissa Muijs
7 months ago
in Jira
0
Future consideration
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
Reut Levi
over 2 years ago
in Jira
1
Future consideration
When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley
over 3 years ago
in Jira
1
Future consideration