Modify workflow to only let a ticket be assigned to someone in a specific Project Role

I have steps in my workflow where only artists should handle these tickets. To make sure nothing gets lost, i was a restriction to only be able to change assignee to someone within the custom project role Art I have.

Is this possible?

4 answers

1 accepted

1 vote
Accepted answer
  1. If you aim is to restrict the assignees when an issue reaches some particular state in a workflow, use workflow properties and set = <<your group name>. (roles are not possible)
  2. If you aim is to restrict the assignee to a project role for all issue types in a project use the Permission scheme as Jason said.
2 votes
Jason Worley Atlassian Team Feb 07, 2013

Thank you for the clarification. In this case, it sounds like a post function will work:

Also, we had a previous post that seems to pertain to your workflow question. I included that link as a reference if interested:

I hope this information was helpful and relevant.

Jason | Atlassian

I don't see anything related to Project Roles on changing the assignee. Only Unassigned, Automatic, or a user.

0 votes
Jason Worley Atlassian Team Feb 07, 2013


If I understand correctly, you wish to restrict those who can change the assignee for an issue.

For the project in question, review the permission scheme and specifically look for:

Assignable User

Users with this permission may be assigned to issues.

Only users or groups with this permission, will be allowed to assign issues.

Please note: the permission scheme will need to be assocaited with a project.

I hope this response allows you to proceed.

Jason | Atlassian

Not who can add an assignee.

Lets say I want to send a ticket to Art.

In the workflow, i want to add a restriction saying that the assignee i add, on this ticket i am sending to art, is in the custom project role Art.

0 votes
Jason Worley Atlassian Team Feb 08, 2013


Thank you for the response. From my experience, the criteria for setting the current assignee would be via the Permission scheme as well as if you leverage a notification scheme. You can copy the default permission scheme, make adjustments to the current assignee (add user or group), then associate it with the project.

I hope this helps.


Jason | Atlassian

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,911 views 19 22
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