History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-4052
Type: New Feature New Feature
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Nick Minutello
Votes: 14
Watchers: 9
Operations

If you were logged in you would be able to see more operations.
JIRA

Jira-to-Jira imports

Created: 16/Jul/04 11:13 AM   Updated: 23/Nov/06 01:55 AM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference

Participants: Anton Mazkovoi [Atlassian], Bernard Cena, Nick Minutello and Tibor Hegyi
Since last comment: 76 weeks, 5 days ago
Labels:


 Description  « Hide
We really need to be able to import projects and all dependant objects (users, groups, permission schemes, notification schemes) from another Jira instance.

We have 2 such immediate requirements at the moment.
1) We have a team using an eval copy and we want to move their issues to our production jira instance
2) We have a team who bought their own copy of Jira - but now they want to move some projects to our production Jira instance

We also have a number of other requirements
1) We have two Jira instances - one in Paris, one in London - and we want to move some London projects to Paris.
2) Likewise, we have some NY projects - and we want NY to have its own server - which means we need a way of migrating the projects to NY at some point in the future.

This shouldnt be too difficult via the SOAP api, no?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Tibor Hegyi - 24/Jun/05 02:54 AM
We have almost the same requirements, ie. having two Professional instances, but we're planning to move to one commong Enteprise instance.
Any suggessions?

Anton Mazkovoi [Atlassian] - 27/Jun/05 11:53 PM
Hi Tibor,

Unfortunately we do not have someting that works straight out of the box for this. However please have a look at:
http://confluence.atlassian.com/display/JIRACOM/Merging+2+JIRA+instances
for possible approaches that can be taken.

Thanks,
Anton


Bernard Cena - 23/Nov/06 01:55 AM
Atlassian dev team,
This is a common request and directly relates to the ability of Jira to scale - are you intending to address this in your roadmap ? The manual method is a painful way to split instances - it's ok as a workaround, but really what is needed is proper migration/archive/restore of entire projects. Yes, we do realise the difficulty with that especially with so many flexible features of Jira and configuration schemes - perhaps a major refactor of the way projects are configured is needed to make this possible if you don't see it possible to migrate a project with all it's dependencies.
Thanks