RELATED IDEAS
Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" field mapping.
After speaking with customer support (hi @Shawn!) and reading some of the documentation, it appears that is due to the inability to "edit" screens in Jira: https://community.atlassian.com/t5/Jira-questions/Create-add-and-edit-screens-in-Agile-board/qaq-p/913674
Perhaps there is a technical limitation on Jira's side, but it does look like this is the direction they are headed so I think it would be good for Aha! to research the feasibility.
-
ADMIN RESPONSEJul 22, 2022
The Aha! + Jira integration now supports Jira next-gen projects. Create a new Jira integration and follow the steps to set it up. When a next-gen project is selected, the integration will see that this is the case and add the default mappings accordingly.
This article provides more detail on how to setup a new Jira integration.
4
MERGED
Manaully Link Requirement to Feature from Integration Updates
We have an integration from Aha to a JIRA "next gen" project. As a result, we have lost the ability to set up a "Link-to" option. So when a Requirement is created in JIRA (for Features that are linked between Aha and JIRA), the new Requirement is ...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Can you provide more info on how this will work now?
Yes please! I'm just starting out, but this software isn't ideal if I can't capitalize on existing work already organized into epics in a JIRA next-gen project. It seems silly to then have to re-organize in both systems...
I'm doing the trial of Aha, and we only use the Next Gen Jira projects. This could be a deal breaker for us as we use Epics to plan the work, and Stories for the dev team. I need the same structure mapped to Master Features and Features in Aha, and have them sync'd together so it's a seamless transition from high to low level planning in Aha, to Jira execution, and back to Aha for completion and release management.
Please add this feature!!
My team has started working with the next gen tools and love them. In my reading about Jira, it appears that they will continue to develop and evolve next gen, which leads me to believe they will deprecate classic at some point. I imagine a next gen/Aha! integration would be quite powerful. I do hope Aha! adds a robust integration with Jira next gen to the roadmap sooner rather than later.
We are also upgraded several our JIRA implementation to the NextGen projects and are unable to leverage links between features and requirements until this is resolved.
I have the same problem
My company already has next gen boards. This is probably a deal breaker. Eliminating double entry is one of the goals.
Just had to compromise and create a classic project - for those of you who know classic you can understand my pain. Would be great to get this happening, especially with assistance from Atlassian as this is a blocker to moving to next gen.
This will be critical for Aha! and Atlassian to resolve together, for our ongoing use of Aha as we are moving many projects onto the lighter-weight Next-gen Jira projects.
Thanks Madeleine from Aha! customer support for pointing me to this idea!
This would be critical to our adoption of Aha.
Same here. We just moved and like the reduced overhead but releases and initiatives aren't linking our stories/tasks to initiatives
Yes, please! We've got multiple dev teams moving from other systems to Jira. We were looking to use the next-gen projects are they are quick to set up and don't have the same overhead as a classic projects.