What we've done in the past is move all component issues to the specific
JIRA-project and then remove the component. Issues shouldn't get lost.If a
project has retired, the project or component should be closed, so people can´t
make new issues but still can access old ones.One problem: jira doesn't support
the 'closed'-state, although there are many votes for such a feature.For that
reason we've marked it as retired (in the title) [1] btw, when moving issues,
please use the bulk change option (under tools in upper right corner of a
search result page) -Robert [1]
https://jira.codehaus.org/browse/MOJO#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel>
Date: Mon, 12 Sep 2011 14:40:05 +0200
> From: [email protected]
> To: [email protected]
> Subject: Re: [mojo-dev] Remove old components from the Mojo project in Jira
>
> I think you should file a jira ticket on the HAUS project asking for
> this jira project.
> If you feel up to it I think the mojo docs could be updated with some
> info about this jira project creation process. As there has been some
> confusion I think it's safe to say it's not totally clear.
>
> /Anders
>
> On Mon, Sep 12, 2011 at 13:34, Christopher Hunt <[email protected]>
> wrote:
> > Sorry one more thing - can you give it the key of MJSLINT?
> >
> > On 12/09/2011, at 9:29 PM, Christopher Hunt wrote:
> >
> >> Hi Anders,
> >>
> >> Actually while you're in there, can you create a JIRA project for JSLint
> >> and remove the MOJO/jslint component - it appears that I don't have the
> >> capability to do either.
> >>
> >> Thanks!
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
