Multiple Workflows for one Project

[Paul Hobbs]

We have a project that is used by our testing team, as well as the vendor's developers and testers. Each defect (ie: issue) can be in one of many different statuses, and there is a clearly defined workflow for each defect. However, occasionally a defect can change to a status that doesn't follow the workflow.

We would like to have a strict workflow which enforces the transitions from one status to another. For example, a defect in the status "In Development" can't transition directly to "In Customer Testing" - it should go to "Ready for Vendor Testing". Anyone can change the status of a defect in line with the enforced workflow transition rules.

We would like a second, relaxed workflow that allows a defect to transition from any status to any status, but only a handful of super-users can change a defect status to something that doesn't conform to the "strict" workflow.

We would configure who can use which workflow through group membership or something similar.

Hope that makes sense.

I suspect I know what the answer will be, but thought I would ask.

[Vishal Biyani]

@Paul Hobbs 

Assume you have two workflows named:

• Strict Workflow
• Relaxed Workflow

Next step will be to configure the workflow permissions. For the required transition, add the condition that checks if user belongs to a specific group

Finally, assign the workflows to Issue Types.

Note: All these steps require JIRA Admin permissions

[Paul Hobbs]

@Vishal Biyani 

That sounds like what I want to do, but I think the problem will be assigning both workflows to a single Issue Type (Bug). Am I correct that I can only assign a single workflow to an Issue Type?

[Vishal Biyani]

@Paul Hobbs 

Good question.

for that you could branch the workflow based on say Teams field or when assignee is in a group or any other custom field. When the condition matches, then only the particular work flow will become visible/active.

[Petru Simion _Simitech Ltd__]

Hi @Paul Hobbs ,

You do not need two workflows.

You will achieve this by adding conditions to your workflow transitions.

The conditions will restrict the transition to only those users or groups or roles that you want to be able to execute those transitions.

Regards, 

Petru