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

Restrict project roles to make move issues between status.

Hello All,


I have following roles and status in the project.

Issue Status: New, In-Progress, Ready for QA, QA Completed, Approved for Release, Completed.

Project Roles: Project Manager, Developer, QA, DevOps


For the issue (Story) the status can be changed by certain roles as defined below.

New -->In Progress (People from any of the project role can change)

In Progress --> Ready for QA (Only people in "Developer" role can change)

Ready for QA --> QA Completed (Only people in "QA" role can change)

QA Completed --> Approved for Release (people in "Project Manager" role can change)

Approved for Release --> Completed (people in "DevOps" role can change).


All people in any project role should be able to see the issues in any of the above status.


Please suggest how to achieve these restrictions.


Thanks and regards,

Santhosh R. Bhat

0 answers

Suggest an answer

Log in or Sign up to answer