Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Comparing Jira Service Desk next-gen and classic

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 14, 2019

Having previous experience with Jira Service Desk classic, you might have a few questions about how it differs from Jira Service Desk next-gen. The post below aims to answer these questions.

Screen Shot 2019-03-11 at 10.34.54 am.png

What are Jira Service Desk next-gen projects?

Next-gen projects are:

  • easier and faster to setup than classic projects. You can easily configure settings like request types and fields with drag-and-drop editing and reordering, all in one place.

  • configured by project team members. Any team member with a project admin role can modify settings of their next-gen projects.

  • contained to themselves. There’s currently no way to associate them with other project settings, schemes, or global configuration objects.

  • only available on the Cloud platform. By default, any licensed user can create these projects. You can change that if you need to.

In classic projects, Jira admins configure a project using schemes to map shared objects to projects, like request types, workflows, fields, and permissions. While schemes maximize the ability to share configurations across multiple projects, they can be difficult to understand for new starters.

Classic projects also leverage objects that exist only at a global level, across your entire Jira site. That makes it easy for Jira admins to push configuration changes across a bunch of projects. But conversely, end users are unable to manage configuration for their own projects. The burden of configuration falls entirely on Jira admins, making it a complex and time-consuming process to customize a project every time a new project or a new team comes to your Jira site.

With next-gen projects, we empower the project owners themselves to customize their projects based on their unique needs without bothering a Jira admin for help.

How do I know if I'm in a next-gen project?

On the bottom of your project sidebar, there will be an icon with the text "You're in a next-gen project," along with a “Give feedback” and a “Learn more” link.

Screen Shot 2019-03-11 at 10.17.15 am.png

Can I read more about upcoming features on next-gen projects?

To find out what's shipped and what's coming for next-gen service desk projects, check out our roadmap.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events