Hi, Bertrand Delacretaz schrieb: > Hi, > > On Thu, Sep 3, 2009 at 1:12 PM, Felix Meschberger<[email protected]> wrote: >> Bertrand Delacretaz schrieb: >>> ...I'd suggest three new states then >>> >>> "Needs documentation/tests" >>> "Needs documentation" >>> "Needs tests" >>> >> ...Should these steps be mandatory, thus no close without transitioning >> through these steps ? Or optional, thuss being able to forget about it... > > Optional..keep things simple, and some issues (like fixing a bug) > don't need docs and tests should be written/updated when fixing the > issue anyway. > >> ...What do we want to capture with the workflow (current states in >> parentheses) ? >> >> * issue has been reported (open) >> * work is in progress (in progress) >> * considered fixed (resolved) >> * confirmed fixed (closed) >> * requires documentation (-) >> * requires test case(s) (-) >> * included in the release (-)... > > Can't we use the JIRA "fix version" field to manage that? > >> ...Which of these states are allowed and how should transitions be allowed >> ? E.g. should a transition from open to "included in release" be allowed ?... > > I'd leave everything allowed for now, we're a small enough team to > manage edge cases manually IMHO.
You are probably right and the presence of the optional steps on the left hand side "menu" might help to not forget about testing/documentation. Regards Felix
