Jira Cloud has launched next-gen projects for Software and Service Desk intending to make our products simply powerful - easier to configure, but even more flexible. Join Peter Grasevski, Developer for Jira Service Desk Cloud, to discover the differences between next-gen and classic projects, how Jira projects will change over the coming years, and what you need to know to keep your app compatible.

1. PETER GRASEVSKI | DEVELOPER | ATLASSIAN | @PDGEE_
What does Jira
next-gen mean for Cloud apps?

2. Jira is complicated
Photo by Rick Mason on Unsplash

3. We want to build a simpler, more powerful Jira

4. Overview

5. Learn about Jira classic
Overview

6. Learn about Jira classic Learn about Jira next-gen
Overview

7. Learn about Jira classic Learn about Jira next-gen
Learn how to keep your apps compatible
Overview

8. Learn about Jira classic
Overview

10. Project: container for issues

11. Project: container for issues
Field: store data
on an issue

12. Project: container for issues
Field: store data
on an issue Screen: collection
of fields

13. Project: container for issues
Field: store data
on an issue Screen: collection
of fields
Status: current
state

14. Project: container for issues
Field: store data
on an issue Screen: collection
of fields
Status: current
state
Workflow: paths
between states

15. Project: container for issues
Field: store data
on an issue Screen: collection
of fields
Status: current
state
Issue type: how
everything is
combined
Workflow: paths
between states

16. Project
Issue type
WorkflowScreen
StatusField

17. Project
Issue types WorkflowsScreens StatusFields
GLOBAL

18. Issue types WorkflowsScreens StatusFields
Project

19. Issue types WorkflowsScreens StatusFields
Issue Type
Scheme
issue types
to be used
Project

20. Issue types WorkflowsScreens StatusFields
Issue Type
Scheme
used in
issue types
to be used
Project

21. Issue types WorkflowsScreens StatusFields
Issue Type
Scheme
Workflow
Scheme
used in
issue types
to be used
maps workflows
to issue types
Project

22. Issue types WorkflowsScreens StatusFields
used on
Issue Type
Scheme
Workflow
Scheme
used in
issue types
to be used
maps workflows
to issue types
Project

23. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
issue types
to be used
maps workflows
to issue types
Project

24. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Project

25. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Projects

26. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Projects

27. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Projects
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

28. Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Projects
Issue Type
Scheme

29. Projects
Issue types WorkflowsScreens StatusFields
Screen
scheme
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
Field config
Field config
scheme
Permissions
Roles
Permission
scheme
NotificationNotification
Scheme
Issue Security
Scheme

32. configure Jira pls?

34. Answer me these questions
three…

37. Project A Project B
View screen Transition screen

40. Oops I’m broken again…

41. Oops I’m broken again…
Board
Issues disappeared from
the board because the
mapped status was
changed!

42. Approvals
Jira Service Desk’s
approvals were
configured on that
status! Now the approval
step is gone!
Oops I’m broken again…
Board
Issues disappeared from
the board because the
mapped status was
changed!

43. Approvals
Jira Service Desk’s
approvals were
configured on that
status! Now the approval
step is gone!
Oops I’m broken again…
Filters
We had 100 filters based
on issues in that status!
Suddenly the issues have
disappeared!
Board
Issues disappeared from
the board because the
mapped status was
changed!

45. Create a new issue type
“Conference talk”, with
the fields:
• Summary
• Number of attendees
YOUR MISSION, SHOULD YOU CHOOSE TO ACCEPT IT…

47. Projects
Issue types WorkflowsScreens StatusFields
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

48. Projects
Issue types WorkflowsScreens StatusFields
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

49. Projects
Issue types WorkflowsScreens StatusFields
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

50. Projects
Issue types WorkflowsScreens StatusFields
Screen
scheme
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

51. Projects
Issue types WorkflowsScreens StatusFields
Screen
scheme
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme

54. You learnt about Jira classic!

55. You learnt about Jira classic!

56. You learnt about Jira classic!
Next up…

57. You learnt about Jira classic!
Learn about Jira next-gen
Next up…

58. How do we make this
better?

65. GLOBAL
Projects
Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types

66. GLOBAL
Projects
Issue types WorkflowsScreens StatusFields
Screen
scheme
used on
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
used inmaps screen
to issue view
maps screen scheme
to issue type
issue types
to be used
maps workflows
to issue types
Next-gen projects
✨
✨
✨
Is WS SF

67. PROJECTScreen
scheme
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
Next-gen project
✨
✨
✨
✨
Issue types WorkflowsScreens StatusFields

68. Screen
scheme
Issue Type
Screen Scheme
Issue Type
Scheme
Workflow
Scheme
Next-gen project
✨
✨
✨
✨
Issue types WorkflowsScreens StatusFields

69. Issue types WorkflowsScreens StatusFields
✨
✨
✨
✨ Next-gen project

70. Issue types
Workflows
Status
Fields
✨
✨
✨
✨ Next-gen project

75. You learnt about Jira next-gen!

76. You learnt about Jira next-gen!

77. You learnt about Jira next-gen!
Next up…
Learn how to keep your apps compatible

78. ASSUMPTIONS ARE
CHANGING

79. Next-gen
Entities are project-scoped, and
are only unique within their
project.
Classic
Entities (statuses, issue types…)
were global and unique
#1: Project-scoped entities

81. LEAKING PROJECT ENTITIES

82. LEAKING PROJECT ENTITIES REVEALING GLOBAL ENTITIES

83. LEAKING PROJECT ENTITIES REVEALING GLOBAL ENTITIES
Example: selecting a field

84. selecting from a
global
context shouldn’t
show
project-scoped
fields
LEAKING PROJECT ENTITIES REVEALING GLOBAL ENTITIES
Example: selecting a field

85. selecting from a
project
context shouldn’t
show
global-scoped
fields
selecting from a
global
context shouldn’t
show
project-scoped
fields
LEAKING PROJECT ENTITIES REVEALING GLOBAL ENTITIES
Example: selecting a field

86. Next-gen
Any user can create a next-gen
project, and the project-scoped
entities within it.*
Classic
Only admins can create/update
entities, and modify project
configuration.
#2: Regular users as project admins
*… if their admin lets them

87. REST API Modules Conceptual
changes
The future
Ecosystem changes

88. REST API
changes
GET project
GET entity
Create/update/
delete entity

89. [
{
...
"id": "10014",
"style": "classic"
},
{
...
"id": "10015",
"style": “next-gen"
},
...
]
REST API
changes
GET project
GET entity
Create/update/
delete entity

90. [
{
...
"id": "10014",
"style": "classic"
},
{
...
"id": "10015",
"style": “next-gen"
},
...
]
REST API
changes
GET project
GET entity
Create/update/
delete entity

91. REST API
changes
GET project
GET entity
Create/update/
delete entity
What can you do with this?
• Change your app functionality based on the
style of project
• Hide or show your app for certain project
styles
• Determine which other APIs to use and how

92. REST API
changes
GET project
GET entity
Create/update/
delete entity

93. [
{
...
"id": "3",
"name": "Task",
},
{
...
"id": "1",
"name": "Task",
"scope": {
"type": “PROJECT",
"project": {
"id": "10000",
"key": "KEY",
"name": "Next Gen Project"
}
}
},
...
]
REST API
changes
GET project
GET entity
Create/update/
delete entity
GET issue types

94. [
{
...
"id": "3",
"name": "Task",
},
{
...
"id": "1",
"name": "Task",
"scope": {
"type": “PROJECT",
"project": {
"id": "10000",
"key": "KEY",
"name": "Next Gen Project"
}
}
},
...
]
REST API
changes
GET project
GET entity
Create/update/
delete entity
GET issue types

95. [
{
...
"id": "3",
"name": "Task",
},
{
...
"id": "1",
"name": "Task",
"scope": {
"type": “PROJECT",
"project": {
"id": "10000",
"key": "KEY",
"name": "Next Gen Project"
}
}
},
...
]
REST API
changes
GET project
GET entity
Create/update/
delete entity
GET issue types

96. REST API
changes
GET project
GET entity
Entity support
• Issue type
• Field
• Status
• Role
• Permission scheme
• Notification scheme
• WorkflowTBD
Create/update/
delete entity

97. REST API
changes
GET project
GET entity
Create/update/
delete entity
What can you do with this?
• Ensure entities aren’t shown in the wrong
context, to avoid users choosing the incorrect
one

98. REST API
changes
GET project
GET entity
Create/update/
delete entity

99. REST API
changes
GET project
GET entity
Create/update/
delete entity
COMING SOON

100. REST API Modules Conceptual
changes
The future
Ecosystem changes

101. Module
changes
App config
pages
Software
boards and
backlog
Issue view

102. Module
changes
App config
pages
Software
boards and
backlog
Issue view

103. Module
changes
App config
pages
Issue view
Software
boards and
backlog

104. Module
changes
App config
pages
Software
boards and
backlog
Issue view

105. Module
changes
App config
pages
Software
boards and
backlog
Issue view

106. Module
changes
App config
pages
Software
boards and
backlog
Issue view
• Glances and panels

107. Module
changes
App config
pages
Software
boards and
backlog
Issue view
• Glances and panels
• Issue fields TBD

108. REST API Modules Conceptual
changes
The future
Ecosystem changes

109. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk

110. Conceptual
changes
Parent-child
relationships
Bug
Issue types in classic
Story SubtaskEpic
Request types in
Jira Service Desk

111. Conceptual
changes
Parent-child
relationships
Bug
Issue types in classic
Story Subtask
Epic
“Epic link” field
Request types in
Jira Service Desk

112. Conceptual
changes
Parent-child
relationships
Bug
Issue types in classic
Story
Subtask
Epic
“Parent” field
“Subtasks” field
“Epic link” field
Request types in
Jira Service Desk

113. Conceptual
changes
Parent-child
relationships
Bug
Issue types in classic
Story
Subtask
Epic
“Parent” field
“Subtasks” field
“Epic link” field
Initiative
“Parent link” field
Request types in
Jira Service Desk
from Portfolio for Jira

114. Conceptual
changes
Parent-child
relationships
Issue types in next-gen
Story
Subtask
Epic
Level
1
0
-1
Request types in
Jira Service Desk

115. Conceptual
changes
Parent-child
relationships
Issue types in next-gen
Story
Subtask
Epic
Level
1
0
-1“Parent” field
“Parent” field
“Parent” field
Request types in
Jira Service Desk

116. Conceptual
changes
Parent-child
relationships
Story
Subtask
Epic 1
0
-1
2
3
…
…
…
…
Request types in
Jira Service Desk

117. Conceptual
changes
Parent-child
relationships
/rest/api/2/project/{projectId}/hierarchy
{
"projectId": "10023",
“hierarchy": [
{
"name": “Base”,
"level": 0,
“issueTypes": [{
"id": 7,
"name": "Story"
}]
},
{
"name": “Epic”,
"level": 1,
“issueTypes": [{
"id": 8,
"name": "Epic"
}]
}
Request types in
Jira Service Desk

118. Conceptual
changes
Parent-child
relationships
/rest/api/2/project/{projectId}/hierarchy
{
"projectId": "10023",
“hierarchy": [
{
"name": “Base”,
"level": 0,
“issueTypes": [{
"id": 7,
"name": "Story"
}]
},
{
"name": “Epic”,
"level": 1,
“issueTypes": [{
"id": 8,
"name": "Epic"
}]
}
Request types in
Jira Service Desk

119. Conceptual
changes
Parent-child
relationships
/rest/api/2/project/{projectId}/hierarchy
{
"projectId": "10023",
“hierarchy": [
{
"name": “Base”,
"level": 0,
“issueTypes": [{
"id": 7,
"name": "Story"
}]
},
{
"name": “Epic”,
"level": 1,
“issueTypes": [{
"id": 8,
"name": "Epic"
}]
}
Request types in
Jira Service Desk

120. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk

121. Conceptual
changes
Parent-child
relationships
Get parent of an issue:
Request types in
Jira Service Desk

122. Conceptual
changes
Parent-child
relationships
Get parent of an issue:
Hit: /rest/api/3/issue/<key>
Check: parent field
Request types in
Jira Service Desk

123. Conceptual
changes
Parent-child
relationships
Get parent of an issue:
Hit: /rest/api/3/issue/<key>
Check: parent field
Request types in
Jira Service Desk
Get children of an issue:

124. Conceptual
changes
Parent-child
relationships
Get parent of an issue:
Hit: /rest/api/3/issue/<key>
Check: parent field
Request types in
Jira Service Desk
Get children of an issue:
Hit: /rest/api/3/search
with JQL: “parent = KEY-123”

125. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk
What can you do with this?
• More consistently find parents and children
of issues

126. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk

127. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk
IT help issue
type
Request types in classic
Hardware
support
Software
support
General
request

128. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk
Request types in next-gen
Hardware
support
Software
support
General
request

129. Conceptual
changes
Parent-child
relationships
Request types in
Jira Service Desk
What can you do with this?
• No longer worry about the difference
between request types and issue types
• Read endpoint will continue to work, write
endpoints won’t - you can use the issue type
one once it’s available

130. REST API Modules Conceptual
changes
The future
Ecosystem changes

131. You learnt how to keep your apps compatible!

132. You learnt how to keep your apps compatible!

133. You learnt how to keep your apps compatible!

134. REST API Modules Conceptual
changes
The future
Ecosystem changes

135. THERE IS STILL A LOT TO DO
THIS IS A MULTI YEAR
JOURNEY.

136. THERE IS STILL A LOT TO DO
THIS IS A MULTI YEAR
JOURNEY.

137. Research
SO WHAT’S LEFT TO DO…?
Envisioning2016
2019
Software
next-gen
Service desk
next-gen
NOW
🎉
🎉

138. Research
SO WHAT’S LEFT TO DO…?
Envisioning2016
2019REST APIs
Software
next-gen
Service desk
next-gen
NOW
🎉
🎉

139. Research
SO WHAT’S LEFT TO DO…?
Envisioning
Workflow
integrations
2016
2019REST APIs
Software
next-gen
Service desk
next-gen
NOW
🎉
🎉

140. Research
SO WHAT’S LEFT TO DO…?
Envisioning
Workflow
integrations
2016
2019REST APIs
Software
next-gen
Shared
configurations
Service desk
next-gen
NOW
🎉
🎉

141. WHY?

142. WHY?
GROW

143. WHY?
GROW
SCALE

144. WHY?
GROW
SCALE
DO BETTER

145. I’d love you to
do a favour
for me…
Create a next-
gen project
Try out your app
in it
Photo by DreamWorks Pictures
If you find
problems, let us
know

146. I’d love you to
do a favour
for me…
Create a next-
gen project
Try out your app
in it
If you find
problems, let us
know
All instances can create Jira
Software next-gen projects.
Head to
<instance>/jsd-next-gen
to enable Jira Service Desk next-gen
Give feedback at:
go.atlassian.com/ngapps
(ACJIRA-1568)
Photo by DreamWorks Pictures

149. Thank you!
PETER GRASEVSKI | DEVELOPER | ATLASSIAN | @PDGEE_
go.atlassian.com/ngapps