[#JRA-2484] Add ability to move projects between installations

JIRA

Add ability to move projects between installations

Created: 16/Oct/03 03:57 AM Updated: 21/Jun/04 11:52 AM

Component/s:

Administration

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Multiple JIRA installations

Issue Links:

Reference

This issue is related to:

JRA-3953 Create Jelly view for issue navigator

~~JRA-3167~~ Option to import/export Single Projects from JIRA.

~~JRA-3447~~ Individual Project Import/Export Option extension to Back-Ups

Participants:	Michael Phillimore-Brown
Since last comment:	4 years, 33 weeks, 2 days ago
Labels:

Description

« Hide

As the use of JIRA grows in a large company, inevitably teams will want to branch off and have their own installations of JIRA (we hope anyway). Inevitably also, managers cannot resist tinkering with their organisations, with teams often moving around within the company.

Therefore, at some point we will want to move projects from one installation to another. Whilst it's easy to split a large JIRA into smaller JIRAs, merging two is not so easy.

So, wouldn't it be great to be able to point one JIRA instance at another and move projects / permission schemes / users etc between them using SOAP or similar? Our need for this is not immediate, but the time will come very soon when this could become a bit of a problem.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Michael Phillimore-Brown added a comment - 05/Feb/04 03:40 AM

Hi,

Please could I bump the priority of this issue up to 'Major'? As we obtain more and more installations, this could start to become a major headache.

Perhaps Jira could produce a jelly script that can be fed into the other instance? Maybe some XSLT wizard wouldn't find it too difficult to take this from the existing export code...?

Cheers,

Mike

[ Permlink | « Hide ]

Michael Phillimore-Brown added a comment - 18/Feb/04 04:40 AM

Would it not be sufficient to create an 'Empty' permission scheme to which nobody has access, then assign the project to that scheme? This way the project is effectively invisible in the system, but you can still go back if you've made a mistake.