nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Different workflows for change requests

Alexander Auer_2fls49

Hello there,

we currently are in the process of evaluating of switching to JSD, but we found an not so nice block in the road.

We have a quite large organisation where we have within a project several change requests. These requests might also have different workflows. Are we right to assume, that different workflows are not applicable in JSD for a change request? We really do want to stay with the concept of issue type.

Are there any best practices how to solve that problem?

Greetings,
Alex

Accepted answers

Udo Brand

As Thomas said you need different issuetypes :

"Change Request for A", "Change Request for B", ...

Be creative :-)

All comments

Thomas Schlegel

Hi Alexander,

if you need different workflows in the same project, you need different issue types.

But in different projects, the workflows for the issue type "Change Request" can be different.

Udo Brand

As Thomas said you need different issuetypes :

"Change Request for A", "Change Request for B", ...

Be creative :-)

H K_4o5qpi

Or maybe you could try something like this and split your workflow path:

Pascal Beaudry

My personal Best Practice, with all my customer,

Validate if is not possible to create more than one type of Change Request.
- If yes, do it, it will be easier to manage
If you really need to have more than workflow, you need to create only 1 Jira workflow that implement the 2 workflows.
- To do that,
  - You need to find a way to segregate your 2 workflows
    - Habitually, you use a select field (1 option), a Checkbox or a radio button Field
  - You need to have a minimum of 1 status in commun between the 2 workflows
  - You have 1 limit, you cant have a transition having the same name but different behavior between 2 statuses
- To implement the 2 workflows in the same Jira Workflow, add a Condition to each of your transition of type "Value Field" (or like this one). Using that you could limit the transition and the statuses available on a workflow depending on a SubType like Customfield.

It's not perfect, but it's working fine.

Alexander Auer_2fls49

We will probably go with that route. Most clean solution in my opinion. Thanks for all the input

Sapna Sharma

After Creating different Issue Types All the Issue are migrated to another Board created.