Restrict transition permission only to current agent assigned


I am trying to find a better way how to allow only the assignee of the issue to perform any transition in my Service Desk Project workflow. What i am trying to achieve is that agents can't access these transitions between each others tickets to prevent missclicks. I know that I can use Condition such as (Current assignee is able to perform this action) on each transition of the workflow to fulfill this request, but I am looking for a better way than set 20 transitions manually - and that is through permission scheme. 

However when i've changed permission scheme from:


Service Desk Team
Service Desk Customer - Portal Access


Current Assignee 

JIRA shows up the error message that this configuration is impacting some core service desk functionalities - in which case I have no idea why is that or what is disruptive in this permission setup. Am i missing something? Is transition permission also linked to Create issue permission which prevents customers from performing create transition? Please let me know if there is something which I do not think of. 


1 answer

1 accepted

0 votes
Answer accepted

Hello Matúš,

The only thing that will not work on the permission you configured is that it must have the Service Desk Customer - Portal Access added to it, otherwise, your customers will not be able to transition issues back to your agents when they answer it.

Although the Administrator and the Service Desk Team can be ignored (You can dismiss the warning), the Customers permission is required to make your Service Desk project works fine. 

Please, let me know if it works for you with those permissions.

"your customers will not be able to transition issues back to your agents when they answer it." - Isn't this based on the automation rule which is triggered by service account attached to Automation section as a default account responsible for the list of rules?

Also, would you solve my problem - "agents can't access these transitions between each others tickets" by permission scheme? Or rather go for conditional approach via Workflow? What should be the best practice here?

Hello Matúš,

About your first question:

The permission Scheme of your project is also applied to customers. That being said, they will not be able to transition back the ticket to your Agents independently of any automation rule that triggers from it (The Automation rules are also executed as the customer triggered it).

For your second question, I believe that if you only add the Service Desk Customer - Portal Access to your permission scheme, your Agents will still not able to access each other tickets unless they are added as customers too, which is not a correct configuration.

That solves this i think! So if w can dismiss that error for Desk Team only then it should work as i requested. 

You are welcome, Matúš.

Have a nice weekend and please let me know if you face any questions regarding this matter again.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

400 views 1 1
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you