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

enable jira-software user to change jsm ticket status


We would like to enable some of our non-agent users (jira-software-users for example) to execute certain transitions on issues that are in a service desk project.

Is there any way to accomplish this? I knew that sharing comments with customers and viewing queues is limited to JSM Agents, but preventing software-users from changing the status is weird. After all it is a Jira issue and if the permission is given to a user to transit or edit, it should be possible.

Thanks for any insight in advance! :)

Cheers, pj

1 answer

0 votes

No, most project functions are limited to the Agents in the project.

The logic behind this is that a Service Desk project is there to handle customer requests, and it's your Agent's job to do that.  The last thing you want is some developer updating status, they aren't there to manage the messaging to the customer.

Well if I allow my developers to come and update a status, I would like to see them be able to do that. And if not, I can always take the permission away from non-agents.

This is not a good excuse. It is obviously a bug or best case lack of proper functionality.

It's neither. Permissions should depend on roles and Nic's answer is appropriate.

On the other hand, if what you want is the activity on your dev's ticket to update back into the JSM ticket, that's more manageable and would not cross the role boundaries as the JSM ticket is updated by automation, not by direct involvement. You might have value by considering this question and its answer:

Like Nic Brough -Adaptavist- likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events