Rework stage
A rework stage is the stage an item returns to when an approval or a review asks for changes. Client review on the design pack names revisions; release approval on the software pack names in progress. The loop is data on the workflow, not a habit.
Without a named rework stage, a request for changes becomes a chat and a new card. With one, the same item comes back on a labelled transition, and the round can be counted.
Still failing on the test cycle pack, still broken on bugfix, and changes requested on code review are the same idea: a named path back.
Perguntas frequentes
- Is rework a stage type?
- No. Rework is usually a work stage that the approval names as reworkStageKey. The type is still work.
- What if I do not name a rework stage?
- The pack you start from already names one on each approval. A workflow you edit should keep that link, or the decision has nowhere to send the work.
- Does rework count as a revision round?
- On packs that count rounds, a request for changes or a rejection consumes a round. The rework stage is where that work then happens.