Remove tedium from changing workflows

Changing a workflow that is currently being used is a tremendously tedious task because you can only change project workflow schemes one at a time (JIRA-5254) and you cannot change a workflow or a scheme if any product is associated with it.

As my company adapts JIRA workflows for our own processes, the workflow edit process is prohibitive. This is what I must do (as I understand it) to make a modification to an existing workflow:

Background: Assume that we want to change workflow W in scheme WS. WS contains other workflows that aren't being changed. And there are at least two projects that use scheme WS.

1. Make a copy of workflow W. Call it W2
2. Make a copy of workflow scheme WS. Call it WS2
3. Remove references to workflow W from scheme WS2
4. Add references to workflow W2 to scheme WS2
5. Go to each project individually and change the workflow scheme to WS2 (see JIRA-5254)
6. Make the appropriate changes to workflow W
7. Go to each project individually and change the workflow scheme back to WS
8. Remove all workflow references in scheme WS2 prior to deleting it.
9. Delete scheme WS2
10. Delete workflow W2

Making all these backup schemes and workflows is necessary because we have added workflow states and they won't be translated correctly unless we create copies.

And then I better hope I built my workflow correctly, because if I made a mistake, I have to go through the entire process again to make even the smallest change.

Requested changes:
1. Bulk project workflow scheme changes (JIRA-5254)
2. Ability to change an active workflow. That way, I could leave my workflow scheme unchanged and not have to create any copies.