Best practice, changing workflow

[Deleted user]

Internal customer wants to change a workflow. There will be the same # of statuses.

The current workflow is not used by any other project.

Would it be best to just edit the current workflow - changing the statuses and transitions to the new ones?

[Kian Stack Mumo Systems · Accepted solution]

I would create a copy of the workflow and make all of your changes on that copy to begin with. To modify your workflow without messing anything else up, you'll need to make sure you aren't changing the global value of a status. The best way to accomplish that is instead of "editing" a status (changing it's name or category), you will want to remove the statuses you don't want from your workflow, and replace them with the ones you do want. Statuses can only be removed from an inactive workflow, which is why I suggest making a copy. Once you have the new workflow how you want it, you can associate it with the project. 

[Deleted user]

Thanks Kian, 

As far as changing the workflow. Best from the project page, "add Workflow" or switch scheme?

[Kian Stack Mumo Systems]

Unless you've already created a workflow scheme for the new workflow, I would just click "add workflow" when viewing the workflows from the project page. Just add the new workflow for the issue types it's needed for. 

[MattS]

If you are comfortable with editing the exported XML of a workflow, you can make very precise changes.

[Deleted user]

Matt, do you know of any documentation regarding completing this?