Detailed evaluation between Jira Service Desk Classic vs Next-gen projects

Patricia Campos

Hi!

Just want to check with anyone who was able to create a full detailed comparison between Classic and Next-gen.

I'm looking for a detailed comparison between the features of the two, like some of the sample below.

• Default language in Classic can be set / changed anytime, but Next-gen has to be setup upon creation.
• Classic has the option to setup automation with Automation and Project Automation, but Next-gen only has the option for Automation.
• Classic provides an option to setup a simplified status label for the customer's view, while Next-gen does not.

Thank you in advance

-Pat

 

Mykenna Cepek

Unfortunately, I'm not sure an up-to-date, comprehensive list exists. Both Classic and Next-Gen project features are constantly changing as Atlassian releases updates.

It would be a great resource if you wanted to create one, though, and share it. Be sure to put a date on it!

Here's a slightly out-of-date summary of some key features (I noticed a few items were inaccurate):

https://community.atlassian.com/t5/Next-gen-articles/Classic-and-next-gen-project-templates-in-Jira-Software-Cloud/ba-p/862404

On the Roadmaps, I see 6 new features planned for Next-Gen in 2020, and one for Classic projects:

https://community.atlassian.com/t5/Next-gen-articles/Classic-and-next-gen-project-templates-in-Jira-Software-Cloud/ba-p/862404

Lots of detail is available on many other Atlassian pages:

https://support.atlassian.com/jira-service-desk-cloud/docs/learn-the-differences-between-classic-and-next-gen-projects/

I assume you're trying to determine the best option for your teams. In my experience (10+ years of Jira usage with teams and Jira administration + team coaching), starting from your high-level needs might be more helpful than a deep dive and comprehensive analysis into all of Jira's features. For example:

• Next-Gen projects can work better to grant teams autonomy for how their board operates, lessening the load on a Jira admin. But Next-gen projects offer far fewer customization options than Classic projects.
• Classic projects have all the bells and whistles that Jira can offer, at the expense of wildly complex customization/administration overhead. Classic projects better support commonality across projects.

I wish I could tell you that you can always easily migrate the team data from Next-Gen to Classic or vice-versa. But unfortunately that is not true (lots of potential for data loss), as documented here:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

Hope some of that helps! Best wishes.