On Thu, May 13, 2010 at 05:52:28PM +0100, Graham Triggs wrote: > I'm actually not a fan of the Closed status. Having worked with Jira in a > number of cases where I've needed to re-organise issues after they've been > worked on - either to add some additional categorisation, re-organisation of > projects, clearing of remaining estimates for reporting purposes - having > items in Closed just causes problems in having to re-open them in order to > move them around. > > Of course, there are swings and roundabouts - having Closed items prevents > people from accidentally affecting the contents - but my experience has been > that Closed isn't that useful. Our needs may well be different though. > > If we want to make a distinction between something being fixed, and being > reviewed, we don't have to use Closed - we could always introduced an > 'Accepted' status that we transition resolved items to once confirmed. Or > introduce [an optional] 'Review' status prior to resolved. There are always > options.
Closing could be part of the release process. When a fix is
incorporated into a release, the issue should be closed. To revisit it
after a release, a new issue should be linked to the old. But I
wouldn't want to do that without an intermediate "reviewed" state.
I think the important states to distinguish are:
o we have an issue.
o someone is working on it. Others should either avoid duplicate
effort or contact the assignee to offer help and receive
coordination.
o assignee thinks the work is done.
o fix is independently tested and judged to work.
o fix is in a release.
It would be nice if the tool could also help us track *where* in SCM
space the fix is incorporated. That is, if it affects several
branches, have all known affected branches (and the trunk) been fixed?
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpDMOxd98qjj.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
