On Jan 9, 2008 7:40 AM, Simon Kitching <[EMAIL PROTECTED]> wrote: > This seems to be a fairly large task for the release manager to do - or is > there an easy way to do a bulk change of jira statuses?
there is a bulk task, yes. > > And what exactly is the benefit? Isn't it just as easy to get a list of > "closed issues with fix-version=x.y.z" as it is to get a list of resolved > issues? the benefit is that users know: -it is resolved (in trunk) but not fixed (in a release) -M > > Cheers, Simon > > ---- Matthias Wessendorf <[EMAIL PROTECTED]> schrieb: > > > +1 I do the same for Trinidad > > > > On Jan 9, 2008 5:54 AM, Manfred Geiler <[EMAIL PROTECTED]> wrote: > > > Common practice in the past was that the release manager sets all > > > "resolved" issues to "closed" after the release is out. > > > > > > --Manfred > > > > > > > > > > > > On 1/9/08, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > > > > > I see that there are quite a few issues in JIRA marked as "resolved". > > > > > > > > The status of "resolved" means that the developer thinks it is now > > > > fixed, and is waiting for either the person who raised the request or > > > > the QA department to check it and then close the issue. > > > > > > > > If you fix an issue, and there is no-one who is going to double-check > > > > it for you, then please mark the issue as *closed*, not as *resolved*. > > > > > > > > Thanks, Simon > > > > > > > > > > > > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > mail: matzew-at-apache-dot-org > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
