Classic vs Next-gen projects... planning for the future

[Tom Synnott]

I can see that next-gen templates are lacking some of the most important features – issue schemes, workflow association etc.

Are these features going to be incorporated into the next-gen templates or, if not, can we continue using the classic templates?

I'm looking to commit to a tool but I don't want to jump in and then end up in a position where classic templates are dropped and next-gen ones don't have the required features.

We do find next-gen valuable, but I wonder will next-gen ever be as powerful as the classic projects? Schemes, workflows and templates would be good to be able to setup.

[Daniel Eads]

Hey Tom, great question.

If you haven't already taken a look, I would encourage you to read through the roadmap for next-gen projects in Jira.

With schemes, the general strategy for next-gen is that projects are independent of one another. This differs from classic projects, where you might share one issue type scheme for example across multiple projects.

Workflow editing is on the roadmap for this year, although the strategy is that workflows won't be shared between projects like you might do in classic.

I hope this provides some insight and that you find the roadmap page useful! This Community article also provides more details on the strategy if you're interested in further reading.

Cheers,
Daniel