Developing for Jira Service Desk Cloud next-gen projects

April 08, 2019 2 min read
Joshua Vernon
Joshua Vernon
Reading Time: 2 minutes

TL;DR
Jira Service Desk Cloud introduced next-gen projects in Feb 2019 and developers may experience some differences when calling either the Jira Service Desk Cloud REST API or Jira platform REST API.

App developers and REST API consumers may need to make modifications to support next-gen projects.

App developers and REST API consumers may need to make modifications to support next-gen projects.

Why is Jira Service Desk implementing next-gen projects?

Next-gen projects are available in Jira and Jira Service Desk, and aim to simplify the project configuration experience for administrators and end-users.

  • Next-gen projects simplify the project configuration experience and allow non-admins to create and configure projects.
  • Project configuration concepts and their application have been simplified without compromising their capabilities.

This blog will focus on the technical impact to Connect App developers and REST API consumers developing for Jira Service Desk.

If you need more information on the impact on developing for Jira please read this blog.

How are next-gen projects different from classic projects?

  • Many configuration entities that were originally globally scoped in classic projects are now project scoped and are created and configured per next-gen project.
    • Jira
      • Project roles
      • Screens
      • Workflows
      • Fields
      • Issue Types
      • Status
    • Jira Service Desk
      • Request Types
      • Request Type Fields
  • Request Types are backed by Issue Types in next-gen projects and can now be retrieved and modified using the Jira platform REST API Issue Type endpoints. This also means Request Type properties are stored as Issue Type properties and can be retrieved and modified using the Jira platform REST API Issue Type Properties endpoints.

What are the REST API changes?

If you are looking for Jira platform REST API changes refer to this blog.

There are no changes to the Jira Service Desk REST API for classic projects. The Jira Service Desk REST API has however been modified slightly to accomodate Next-gen project and project scoped entities.

  • Read operations for Request Types will keep working in next-gen projects, however, mutation operations will not and the Jira platform REST API Issue Type endpoints should be used instead.
  • Approvals and Customer Transitions are being revamped in next-gen projects and will return not implemented errors when used with next-gen project scoped entities in the meantime.
  • Jira platform REST API read operations for all project scoped configuration entities shared between Jira and Jira Service Desk will continue to work per contract, however, mutation operations will fail. Visit the Jira Cloud Platform API public roadmap to see when these API's will be updated.

Stay in touch

Next-gen projects are being improved each and every day and will soon be as powerful and then more powerful than classic projects from user and developer perspectives. Read and give us feedback by watching or using the next-gen tag in the Atlassian Developer Community.