Hi, For me I use "closed" to figure out if an issue was just committed or if there is already a release out there. So to me it is natural to close all issues after the release. It's just a bulk change, takes like 2 minuten per project (most of the time is setting the filter and then clicking through the bulk change API).
Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Erick Erickson [mailto:[email protected]] > Sent: Friday, April 7, 2017 6:40 PM > To: [email protected]; Christine Poerschke > <[email protected]> > Subject: Re: Resolved --> Closed transition for 6.4 release issues > > My question is "Why do we even have two?". > > If we don't have any real use for having both, I'd vote for removing one. > > I see Steve's comment but would still ask whether having two serves > enough good purpose to be worth the confusion. Does anyone really > _use_ this distinction? Or is it just another thing to get wrong when > resolving a ticket as well as be another task for the RM? > > Don't particularly have any strong feelings here, but thought it worth asking. > > Erick > > On Fri, Apr 7, 2017 at 9:32 AM, Christine Poerschke (BLOOMBERG/ > LONDON) <[email protected]> wrote: > > Hi Everyone, > > > > Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA > issues works? > > > > I just noticed that some 6.4 tickets are still marked 'Resolved' rather than > 'Closed' which surprised me. This JQL finds them: "status = Resolved and > project in (LUCENE,SOLR) and fixVersion=6.4" > > > > Thanks, > > Christine > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
