Next Gen sprint(s) not appearing at all in Sprints field in Automation for Jira

[Dan H]

When setting up an Automation to assign issue to active sprint upon issue creation, I can't find and select the actual sprint for our Next Gen project in the drop-down list at all.

The list only displays all sprints across the board for projects setup using older/current Jira.

As you can see in the screenshot, our Jira is full of several projects each containing many different sprints BUT our only Next Gen project (sprint) we we wish to use does not exist in this list at all :(

Just to note, I've tested the automation and it works perfectly (I tested by selecting any sprint from another project). So the issue is literally just being able to choose the correct sprint for the Project this automation is only being created for.

[Petter Gonçalves · Accepted solution]

Hello @Dan H

Thank you for reaching out.

Indeed, Next-gen projects use a different mechanism to link Sprint to issues which the Automation rules are not able to recognize yet.

Basically, this happens due to the fact that Next-gen projects use single entities for each project scope (Sprint, status, etc), so a different field was created to link Next-gen Sprints.

We have the following feature request to allow the Sprint field in Automation rules to display options of Next-gen Projects:

Support nextgen sprint options in sprint field picker 

If you are using Next-gen, I'm afraid we don't have a way to make it work with Next-gen projects at this moment, so I recommend you keep an eye on the feature request and move your issues to a Classic project.

Let us know if you have any questions.

[Fowler]

Wait, so you all built a whole new automation engine, offering it up as a solution to all sorts of limitations for next-gen projects, and then you forget to support next-gen projects and tell people to "move your issues to a classic project"

Did I get that right?

[Sam Mohyee]

@Fowler I believe you've got that right. Welcome to the exciting world of Next Gen projects, where the motto is: "Oh, someone is still actually using this? And they think they deserve functionality!?"

[Petter Gonçalves]

Hello @Fowler  and @Sam Mohyee

Sorry for my late reply. Please, allow me to bring you some context about Jira Automation and why we are still working to support some of the features in Next-gen:

Jira automation is not a functionality built from the very beginning by Atlassian, but an app from a third-party vendor that was acquired by Atlassian a few months ago:

Atlassian acquires Code Barrel, makers of Automation for Jira 

That being said, this app was developed years before Next-gen projects were even considered in the Jira roadmap. For that reason, it was originally created to work only with Classic projects.

With the acquirement of the app by Atlassian, our developers are currently working to enable this feature to be fully integrated with the specific architecture of Next-gen. Some of the architecture aspects of next-gen are considered as unique identities, which is a real challenge when working to integrate with Jira Automation.

While we work to get this feature fully integrated with Next-gen, please keep providing us with your feedback so we can better prioritize our efforts.

Thanks!

[Fowler]

@Petter Gonçalves Thanks for the background - I must have missed the Code Barrel acquisition, but that helps put it in context. I still remember the challenges that was the transition from Greenhopper as a third party plugin, to the acquisition and finally the rebranding into Jira Agile. 

I say this every chance I get: Next-Gen is horribly branded. I've been using Jira (and confluence) since 2007 and was really excited based on the branding. I've been continually disappointed to find out that Next-Gen is actually "Jira Lite" and not "Jira 2.0"

[Petter Gonçalves]

Hello @Fowler

Thank you for all the feedback provided.

Indeed, Jira Next-gen was initially created to be a simpler version of the Classic Jira, designed to those customers looking for a straight forward solution with fewer options of customization (Similar to Trello). Maybe the name "Next-gen" gave the incorrect expectations for this template.

Anyway, we are considering all the feedback provided and coming to the conclusion that it's not a simpler solution that most customers are looking for, but a way to turn off/on any features based on the requirements of your scenario. That's why our developers are implementing some of the required features originally implemented in Classic Jira:

Next-gen Roadmap 

Additionally to that, Next-gen projects also has its functionalities based on unique identities, which will make it easier to be handled and migrated from one environment to another in the future, as the "single project migration" is something required long ago in Jira Cloud.

We're sorry to see you are disappointed and that Next-gen does not match your expectations today, however, we hope that our improvements and efforts can change your mind in a close future.

Have a nice weekend! :)