Forums

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

How to set different flows to different roles?

Hadas Hamerovv
Contributor
June 21, 2021

Hi,

Can I set different flows to different flows under the same issue type?

For example: I want a QA personnel be allowed to move a bug from status 1 to 'closed' but prevent the developers from doing so.

 

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 21, 2021

Workflow is done by issue type, not by role.

But you can do what you need.   Build your workflow such that it supports all the transitions you need between status.  Then add "conditions" to it that only allow certain roles to do certain things.

For the example you've given, have a transition from 1 to 'closed' and add a condition for "user must be in the role of QA-personnel"

Hadas Hamerovv
Contributor
June 21, 2021

Thanks Nic for the quick reply.

Where do I find the conditions?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 21, 2021

When you go to edit the workflow, you'll find it is a set of steps (labelled with their Status in both text and diagram mode) and transitions (the arrows between them in the diagram).  If you click on a transition, there will be a box with a set of tabs - conditions, validators, post-functions and triggers.  Hit the conditions one and you'll find an "add condition" button there.

Hadas Hamerovv
Contributor
June 21, 2021

Thanks Nic. You the man.

I did not notice it when created the flow. Will go there again and check.

Hadas Hamerovv
Contributor
June 22, 2021

Looks perfect.

I added two conditions:

Either if one of a roles

or

The creator of the bug.

 

Thanks Nic. You helped so much.

Suggest an answer

Log in or Sign up to answer