I was thinking the same thing, just move all the issues. But I'm not sure how this would affect the change log of releases in the Mojo project.
On 04/13/2011 01:42 PM, Robert Scholte wrote: > why not all? This way you can delete the component so you're sure > there's only one place where people can post issues. > > -Robert > >> From: [email protected] >> Date: Wed, 13 Apr 2011 19:43:53 +0200 >> To: [email protected] >> Subject: Re: [mojo-dev] new jira project for build number (was Re: > [mojo-dev] [ANN] Release Buildnumber Plugin 1.0) >> >> thanks ! >> I have only moved the open issues. >> >> /Olivier >> >> 2011/4/13 Robert Scholte <[email protected]>: >> > After a search in the upper right corner: Tools > Bulk Change > all 63 >> > issue(s) >> > 63 is the number of issues for the mojo project/buildnumber component. >> > >> > -Robert >> > >> >> Date: Wed, 13 Apr 2011 09:20:03 -0500 >> >> From: [email protected] >> >> To: [email protected] >> >> Subject: Re: [mojo-dev] new jira project for build number (was Re: >> >> [mojo-dev] [ANN] Release Buildnumber Plugin 1.0) >> >> >> >> If you go to the advanced search, you should be able to search the Mojo >> >> project and select the component "buildnumber". Then just do a batch >> >> update to move them all. >> >> >> >> On 04/13/2011 03:18 AM, Olivier Lamy wrote: >> >> > Brett, >> >> > Any batch way to move issues from MOJO (buildnumber component) to the >> >> > new project ? >> >> > >> >> > /Olivier >> >> > >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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 >> >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
