The use case here is quite simple:
- The user has a list of tasks (first image)
- Each task has a set of steps (second image - opened in a "drawer" of sorts)
- In order for a task to be completed, the user has to mark all of its steps as complete.
- The logical progression of the steps - "step 1" has to be completed before "step 2", and so on.
- Clicking "Complete" on a Step "enables" the next step, and allows the user to Complete it. Once every step is complete, the task status is set to complete as well.
The doubts/issues I'm having with the current design revolve around:
- If user hits "Complete" on a step by mistake, there should be a way for them to edit it after the fact.
- If the previous is true, what happens when a user has Step 1 through 4 completed, but needs to revert Step 2 to "Incomplete"(an edge case, yes, but it was brought up in a demo and I need to address it)? The only logical thing to do in this case would be to disable Steps 3 and 4 until the user completes Step 2.
What I'm looking for is:
Some critique/validation/input on the UX/Design.
Suggestions on how to solve issue #2 above.