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; } } }

I can see Issue types which are not Present In my Projects when I try to Switch Workflow Scheme.

Arjunsingh Hajari

When I try to Switch the Workflow Scheme in one Project the next step asks me to map the Issue type to the statues where the issue types are not from the same Projectand also checked the Workflow Scheme is not Shared.

So I need to go to the Workflow Scheme and associate each Workflow to each Issue type separately.

Can anyone tell me is this a good Approach to associate the Workflows to Issue type? Which I am doing.

Also I think the reason I can see other Issue Types is they might be using the same Workflow in some Other Project,but if this is the case will this also change the Workflow for the Issue types for Other Project?

Accepted answers

Moses Thomas_08kyb0

@Arjunsingh HajariWe have a documentation below here, please read you will find your answers here. Configuring workflow schemes

Best!

All comments

Moses Thomas_08kyb0

@Arjunsingh HajariWe have a documentation below here, please read you will find your answers here. Configuring workflow schemes

Best!

Arjunsingh Hajari

@Moses Thomas Thanks for the documentation but I did not find the answer of my question in the documentation.

Moses Thomas_08kyb0

@Arjunsingh HajariLet me explain, every issutype can have its own workflow, if a workflow is use by different issue types in different project. then go to workflow when log as admin, you will see all work flow schemes this workflow is used in then click the scheme there you can dis associate work flow from issue type.

If you associate a workflow used in other projects, with an issue type in other projects this will not destroy anything in other projects, but you need to have workflow scheme.

If you change a workflow scheme used in multiple projects, the new workflow scheme which you have just added will be used by this project

Best is to create a workflow scheme for this particular project and associate workflows to issue type. then associate it to the project.

I hope this is clear.

Best.

Arjunsingh Hajari

@Moses Thomas Thanks for such a great explanation this is really helpful also I want to ask as I am doing the Issue type migration in past we used 14 Issue types and now we are using only 8 So the Workflow scheme which was used in past was for 14 Issue types. So I have assigned the new 8 Issue-types to the current workflow scheme.

But still I can see the previous 14 Issue types are using the same Scheme So what is the good approach as I dont want to touch or tear the previous configuration.