Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Berat Altunhan
Contributor
May 8, 2023 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
Community Champion
May 8, 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! 

Berat Altunhan
Contributor
May 8, 2023

Thank you ! I solved it. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
atlassian, aafp, jira migration, marketing collaboration, end siloed work, streamline workflows, kerrie gottschalk, jira cloud admins, unified marketing, process visibility, team efficiency, cross-team collaboration

How Kerrie Gottschalk unified AAFP’s marketing team with Jira

At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.

Read the story
AUG Leaders

Atlassian Community Events