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.
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
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
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!
44.
45. Create a new issue type
“Conference talk”, with
the fields:
• Summary
• Number of attendees
YOUR MISSION, SHOULD YOU CHOOSE TO ACCEPT IT…
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
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
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
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
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
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
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
🎉
🎉
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