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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,464,912
Community Members
 
Community Events
176
Community Groups

Adding Stakeholders and Responders to Services

Hey,

On my personal instance it is automatically set up so that when creating a new service in JSM you can also add responders or stakeholders:

image.png

 

When checking a much mature cloud instance I do not get the option to add stakeholders and responders:

image.png

 

Slightly confusing as both are cloud deployments of JSM so all updates are automatically rolled out. But it seems like the mature instance is not up to date with the latest features. Could someone let me know if they have experienced this?

 

I have cross-checked both instances and cannot see any settings etc that could be stopping this from working.

Thanks in advance.

1 answer

0 votes
Brant Schroeder Community Leader Dec 01, 2022

@forbeslistsoon 

You can turn on the stakeholder function if you go to Project settings > Incident management for the project that is missing this functionality. Have a look at this article for more information, Next level incident management in Jira Service Management .

Seems like the instance had releases set to bundled rather than continuous - so it just needed updating. Resolved now but thanks for the response. Appreciated!

Like Brant Schroeder likes this
Brant Schroeder Community Leader Dec 08, 2022

@forbeslistsoon can you accept the answer to help others.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events