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

[Arjun Hazari]

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?

[Moses Thomas · Accepted solution]

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

Best!

[Arjun Hazari]

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

[Moses Thomas]

@Arjun HazariLet 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.

[Arjun Hazari]

@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.

[Moses Thomas]

@Arjun HazariIf  issues are create with  any  of these issue types in  14,   then is better  not to  remove issue types from  the issue type scheme, because if  you  will  remove them then  you  will  have to  migrate all  issues to  any of the 8 issue types which  you  want  to  use for  this project.   As for the work-flows,  issue types will  use the work-flow scheme which  you  have  set in your association.

So in my opinion  best  you  leave it as it was  with 14 issue types  not to  mess with  issues  if at all there is , but as i have mentioned   you can  associate any work-flow with  any  issue type.

Best!

[Arjun Hazari]

@Moses Thomas Yes your are right .

I have migrated the Issues to other Issue types and the team has said they are fine with that.

The concern is of Workflow Scheme and the Custom fields I think there might be Probable data loss if the Issue types are changed and the Context will be missed by the new Issue types.

And I am just adding the new Issues to the same Workflow scheme so will this affect any other Projects?

[Moses Thomas]

@Arjun Hazari

I have mention  what  will  happen  if  you  remove issue type.

There will not be effect to other projects as long  as they  are not using this issue  type scheme.

I have explain  about work flow.

As  for custom fields   if you  migrate issue  using  a particular issue type,  to  anothe  project, then  if this field are not  in  the screen(for instance edit, view)  then it will  not be shown  in these screen, you  will  have to  add the field to  screen.

[Arjun Hazari]

Thank you @Moses Thomas

[Moses Thomas]

@Arjun HazariYou are welcome,  could you mark solution as accepted/vote  so that  others could  benefits  in case they ran  into  similar situation.

Best!.