> On 3 Sep 2009, at 10:04, Vidar Ramdal wrote: > > > On Thu, Sep 3, 2009 at 10:38 AM, Bertrand > > Delacretaz<[email protected]> wrote: > >> 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? > > > > +1 > > > > yes +1, provided that the workflow transitions are simple and > easy to > use. I used a more complex Jira setup where it was never > clear how and > where to transition to.... it was a nightmare to use without a cheat > sheet on the wall.
+1 best regards mike
