Support "Agility" (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:

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. 

  • Jordan Skole
  • Oct 18 2018
  • Future consideration
Release time frame
  • Attach files
  • Wes Gillette commented
    December 06, 2018 19:38

    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. 

  • Lenny Fayard commented
    December 16, 2018 21:52

    Same here.   We just moved and like the reduced overhead but releases and initiatives aren't linking our stories/tasks to initiatives

  • Matt Clower commented
    February 19, 2019 22:15

    This would be critical to our adoption of Aha.

  • Daniel Cunningham commented
    April 30, 2019 15:35

    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!

  • Guest commented
    June 18, 2019 01:57

    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. 

  • Brett Johnston commented
    June 20, 2019 21:03

    My company already has next gen boards. This is probably a deal breaker. Eliminating double entry is one of the goals.

  • Kote Khutsishvili commented
    November 04, 2019 12:26

    I have the same problem

  • CJ Jacobs commented
    November 26, 2019 19:49

    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.

  • Ilka Pritchard commented
    December 20, 2019 17:48

    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.

  • Chris Brooks commented
    18 Feb 18:28

    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!!