Currently, on production works there is two buttons:
- Start → Which creates a cycle and updates the work state to ‘running’
- Stop → Which finish the cycle and sets the work state to ‘done’.
This was discussed in Simplify start and finish of production works
But the problem is that the Stop behaviour is not always what the user wants. Sometimes the user knows that the works is still not done and he must continue working on it tomorrow (or another day).
This can be implemented by creating a new cycle in draft status, but this is not intuitive from the user point of view.
I’m wondering if it won’t be better to:
- Rename the current stop to “Finish” so it is clear that the work will be set to done.
- Create a new button called “Pause”, which will finish the current work and create a new draft one so the state is keep as “Waiting”.
Also, the start button should be updated to do not create a new Cyclye if draft, but just set them as running.
Does it make sense? Any better ideas?