If the versions are used appropriately, then this reporting should be able to be done after the release, since new bugs won't get fixed in a released version. You could then filter by date as well since you know the date of a release, and could save and share the filters.
In my experience, grouping issues into the one category to allow filtering makes it more difficult to track actual bugs vs tasks as you lose the more granular reporting. cheers, Steve On 26/07/2012, at 6:38 AM, Lance Speelmon wrote: > I would like to track all bugs filed against a release after it has shipped. > I think this is an important quality metric that is currently being obscured > by the fact that we have nearly 200 bugs for 1.4 and it has not even shipped. > :) > > Unless someone strongly objects, I would like to migrate all existing 1.4 > bugs to a different JIRA type - maybe task. This will allow us to track the > number of new bugs filed against 1.4 after it ships. WDYT? > > +1 Thanks, L > > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
