Another way to do it is to simply rename the version 1.10 to 1.9.1 in JIRA. That works well if all the issues should be moved, as is the case here.
Robert Scholte wrote: > http://jira.codehaus.org/secure/IssueNavigator.jspa > project: Qdox > Issue Type: Any > Fix For: 1.10 > > and you'll get 13 issues: > in the upper right corner: Bulk change all 13 issue(s) > > then check them all, followed by Edit Issues, which is not available for me > > - Robert > > > ------------------------------------------------------------------------ > From: [email protected] > To: [email protected] > Date: Sat, 25 Apr 2009 07:49:16 -0700 > Subject: Re: [qdox-dev] request for next qdox release > > OK, someone give me the skinny : move which issues en-masse to which > version number. > > Regards, > > - Paul > > On Apr 25, 2009, at 7:32 AM, Robert Scholte wrote: > > I've done it with one of my own introduced tasks, but it just didn't > felt right. So I had a look on jira-documentation and I think > there's a better way to change it: bulk operations > > http://www.atlassian.com/software/jira/docs/latest/bulkoperations.html#Steps+to+Perform+Bulk+Operations > One issue: you need to have enough permissions to be able to change > these issues. (and you guessed right: I don't have them) > It looks quite easy (and fast! :) ) so could one of you try to > change the fixed version this way? > > regards > > - Robert > > > > To: [email protected] <mailto:[email protected]> > > From: [email protected] <mailto:[email protected]> > > Date: Sat, 25 Apr 2009 13:58:35 +0100 > > Subject: Re: [qdox-dev] request for next qdox release > > > > Robert Scholte wrote: > > > Hi Mauro, > > > > > > thanks for your action. And yes, it would be nice if you could > move the > > > issues to 1.9.1 > > > > Actually, I was mistaken. I thought I could do a move, but that > applies > > only to inter-project moves. In our case, we need to edit the issues > > one by one and change the fix version to 1.9.1. > > > > As they are assigned to you and would have to re-assign them to edit > > them and then re-assign them to you (credit where credit due!), > perhaps > > easier if you do it. > > > > > About the 1.9.2 or 1.10, I don't have the experience yet to know > what > > > works best. > > > From my point of view it looks easier if you go to 1.9.2 and while > > > you're working on issues can decide if it's better to release > > > a non-minor, pushing it to 1.10 instead of the other way around > (going > > > back from 1.10 to 1.9.2) > > > It's minor thing, so let's go for the 1.10 > > > > If we know already we're doing a 1.9.2 and not a 1.10 then it does > make > > sense to have a 1.9.2-SNAPSHOT and assign issues to 1.9.2 in Jira. > > > > > > If we have yet decided, then let's keep 1.10. > > > > I'm fine either way. > > > > Cheers > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > ------------------------------------------------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger > <http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/> > > > > ------------------------------------------------------------------------ > See all the ways you can stay connected to friends and family > <http://www.microsoft.com/windows/windowslive/default.aspx> -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
