Advice needed about Workflow change

[Ximena]

I need advice about the way I change my workflow.
I copy the existing one and on the copy, I add new statuses if needed with new transitions.  I do not delete the statuses not needed (but delete the transitions to them) so when I do the bulk change the old statuses of issues before workflow change remain the same. 
This is very helpful when the new workflow is very different to the old one and statuses cannot be related to the new ones. 

I would like to have an expert opinion on what can go wrong with this method.

[Tim C]

To prevent having "stuck" tickets that can't be transitioned ... I'd suggest adding a "cancelled" status (or similar) into your workflow and then map all of the "abandoned" statuses onto cancelled instead so the status for those tickets get updated whenever the new workflow gets applied to your project (and effectively get removed from appearing in an "active" state).

In your way, people would still find & see the data in these abandoned status when doing queries/searches.  Keeping "noise" is probably never recommended.

If needed, you could add a condition on the transition to "cancelled" so it doesn't appear to normal users (and also ensure the "resolution" field gets set during post-processing on this transition - so these abandoned tickets appear resolved/closed).

[Jack Brickey]

Why do you wish for the old statuses to remain? Unless you use the "all" transition to one or more of the statuses associated with the workflow then any issue that is in an old "abandoned " status cannot be transitioned. It would seem to me that you would want every issue in an old "to be abandoned" status to be re-associated to a new workflow status, as part of the process of editing the workflow.