I've tried and seems that bulk change only allows delete and edit. There are about 83 issues to be closed so please tell me if I'm wrong.
I will close them with "cannot reproduce" > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 22, 2004 8:04 PM > To: Maven Developers List > Subject: RE: movement of issues in JIRA > > On Thu, 2004-07-22 at 13:51, Carlos Sanchez wrote: > > Ok > > > > What about bulk closing old issues, e.g. older than january? > > Sounds good to me, close 'em down. If those closed issues are > not opened again in a few months then we can nuke them. > > > > -----Original Message----- > > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, July 22, 2004 6:04 PM > > > To: Maven Developers List > > > Subject: movement of issues in JIRA > > > > > > Hi, > > > > > > I have moved all the existing issues that were placed under > > > 1.1 to unscheduled. > > > > > > There are 11 issues listed for 1.0.1 but I'm not sure they > > > accurately reflect what will actually be done for 1.0.1. If you > > > placed any issues in there and you are going to tackle them for > > > 1.0.1 then that's cool. > > > Otherwise please move them out and into unscheduled so we > can make > > > an accurate roadmap. > > > > > > Brett is doing a little sight seeing at the moment but we'll be > > > doing some planning later on about releases of 1.0.1, 1.1 > and m2 so > > > if you know there are things you want to work on for > either of those > > > releases then move them into the appropriate version so the > > > generated road map will be accurate. > > > > > > I would also like devs to look at the form layout for entering > > > issues that m2 and xstream have: most of the crap from > the form has > > > been removed in an attempt to make things more clear i.e > most of the > > > time management stuff and environment fields are useless. > One thing > > > I have not figured out how to do is optionally disable a > field. In > > > this particular case it's the version field where I don't > want users > > > being able to assign versions, devs do this when they are > ready to > > > work on them for a release. All issues entered by users > go into the > > > unscheduled category. What is there for > > > m2 and xstream as far as setup goes is what I would like > to do for > > > maven so please take a look if you have a moment. > > > > > > -- > > > jvz. > > > > > > Jason van Zyl > > > [EMAIL PROTECTED] > > > http://maven.apache.org > > > > > > happiness is like a butterfly: the more you chase it, the more it > > > will elude you, but if you turn your attention to other > things, it > > > will come and sit softly on your shoulder ... > > > > > > -- Thoreau > > > > > > > > > > -------------------------------------------------------------------- > > > - 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] > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://maven.apache.org > > happiness is like a butterfly: the more you chase it, the > more it will elude you, but if you turn your attention to > other things, it will come and sit softly on your shoulder ... > > -- Thoreau > > > --------------------------------------------------------------------- > 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]
