> management stuff and environment fields are useless. One thing I have
> not figured out how to do is optionally disable a field. In this
For the record, I think this just works. Fields only appear if the user has
permission to edit them.
Just be careful not to make one of these fields compulsor
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-
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
; > 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
> >
Ok
What about bulk closing old issues, e.g. older than january?
> -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
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: jeudi 22 juillet 2004 18:04
> 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
>
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.
O
