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,555,789
Community Members
 
Community Events
184
Community Groups

The person who brings the issue to Resolved status should not be the same as the person next status.

Edited

Hi everyone,

I am currently working on a workflow and this workflow holds a lot of statuses. But at one point I want to do, I cannot do the condition I want on the relevant transition. It would be more accurate to explain it through an example.

I have a project, 6 people are attached in this project. The person who brings the issue to Resolved status should not be the same as the person who brings it to Deployed status. In other words, if person X has brought an issue to Resolved status, I want other people in the team to bring this issue to Deployed status.

Is it possible to do something like this?image_2023-05-08_115302761.png

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 08, 2023

Hi @Berat Altunhan,

Have a look at the separation of duties condition to implement this. It implies that a user who performed a previous transition between 2 statuses should not be allowed to execute the next transition, which looks very much what you explain here.

Hope this helps! 

Thank you ! I solved it. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events