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

Key: JRA-3447
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Ant Adam
Votes: 7
Watchers: 3
Operations

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

Individual Project Import/Export Option extension to Back-Ups

Created: 23/Mar/04 09:30 AM   Updated: 16/Aug/05 12:04 AM
Component/s: Import / Export
Affects Version/s: 2.5.3 Professional
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Jira 2.5.3 Pro Standalone tied to Oracle 8.1.7, JDK 1.4.1_02, Windows 2K
Issue Links:
Duplicate
 
Reference
 

Participants: Ant Adam, Nick Menere [Atlassian], Richard THIBAULT and Scott Farquhar [Atlassian]
Since last comment: 143 weeks, 2 days ago
Resolution Date: 16/Aug/05 12:04 AM
Labels:


 Description  « Hide
A customer has requested that we provide an XML export of those products they have purchased from our Jira install so that they can import them into their Jira for read only browsing locally behind their firewall.

Currently, the import/export appears to say that it clears the database down and recreates from the back up. This is of insufficient granularity to provide the ability to move easily projects between Jira installations.

As we have encouraged the customers to go with Jira, can we encourage you to provide project level import/export where only the project being imported is blasted and not the whole database?

Many thanks if this is possible.

aadam@ludologic.com



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 25/Mar/04 12:45 AM
You can export the whole database, import into a new instance, and then delete the projects that you are not interested in.

Does this work for you?


Richard THIBAULT - 26/May/04 04:18 PM
We have the same need.
We plan to have 2 instances in production and we already know that some projects will need to move from one instance to another.
Your proposition cannot work since we need to import some projects in a JIRA instance that already contains other projects...

Nick Menere [Atlassian] - 16/Aug/05 12:04 AM
Resolving as a duplicate JRA-1604