New workflow states start in progress instead of not started
I haven't been able to test permissions past the "Edit" phase (see #133 (closed)), but in the first few steps, marking a workflow step as complete advances the workflow status so that the next workflow state is in progress (the step shows arrows to indicate it's in progress).
From there, the person who has permissions to change the workflow state can roll back the status one step to a new workflow state. In this new state, the previous step remains marked complete, but the current workflow step is no longer in progress.
It is worth discussing whether marking a previous step complete should change the next workflow state to in progress automatically. I would argue that we probably don't want to do that. Instead, my vote is that the current workflow state should be marked complete and the next step should not be in progress until the next actor comes and marks it as such:
- New workflow steps starting "in progress" isn't quite as accurate as having the next actor set the state. Moving the workflow state from not started to in progress is a good indicator to other people that the next person has seen that the chapter's ready for their work. For example, the production editor could see that the copyeditor has started his or her work.
- It seems unexpected that one workflow step forward (moving currently in progress task to complete and setting the next workflow state to in progress) takes 2 steps back to undo (next step moves from in progress to not started, then the next step back moves the previous workflow step from complete to in progress).
@Alison @julientaq @alexgeo what do you think?