Hi, Bertrand Delacretaz schrieb: > Hi, > > On Thu, Sep 3, 2009 at 10:22 AM, Jukka Zitting<[email protected]> wrote: >> On Thu, Sep 3, 2009 at 10:12 AM, Bertrand >> Delacretaz<[email protected]> wrote: >>> ...does JIRA allow for "needs documentation" (and maybe "needs >>> automated tests") states for such issues, where the coding is done but >>> docs and/or tests are still missing. >>> >> ...It's possible to specify a custom Jira workflow for something like >> this. Just define the extra issue states you need and the permitted >> transitions between the states. The default states used currently are: >> Open, In Progress, Reopened, Resolved, Closed.... > > I'd suggest three new states then > > "Needs documentation/tests" > "Needs documentation" > "Needs tests" > > Transition from any state to these would be allowed, and these can > transition to any state except "Open". > > What do people think?
Basically, +1. Should these steps be mandatory, thus no close without transitioning through these steps ? Or optional, thuss being able to forget about it 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 (-) * closed (closed) 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 ? Regards Felix
