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

Key: JRA-12447
Type: New Feature New Feature
Status: Closed Closed
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Joop
Votes: 0
Watchers: 0
Operations

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

Separate export/import of configuration and data

Created: 27/Mar/07 01:26 AM   Updated: 28/Mar/07 07:55 PM
Component/s: Import / Export, Workflow, Project Management
Affects Version/s: 1.4, 1.4.1, 2.0, 1.4.2, 3.2, 1.4.3, 2.1 Enterprise, 2.0.1, 2.0.2, 2.1 Pro, 2.3 Enterprise, 2.2 Pro, 2.2 Enterprise, 2.3 Pro, 2.2.1 Pro, 2.4 Pro, 2.4 Enterprise, 2.5 Pro, 2.5 Enterprise, 2.4.1, 2.5 BETA, 2.5.1 Professional, 2.5.1 Enterprise, 2.5.2 Professional, 2.5.2 Enterprise, 2.6 Pro, 2.6 Enterprise, 2.5.3 Professional, 2.5.3 Enterprise, 2.6.1 Pro, 2.6.1 Enterprise, 3.1 Pro, 3.1 Enterprise, 3.0 Professional Beta, 3.0 Enterprise Beta, 3.0 Standard Beta, 3.0 Standard Final, 3.0 Professional Final, 3.0 Enterprise Final, 3.1 Standard, 3.0.1 Standard, 3.0.1 Professional, 3.0.1 Enterprise, 3.0.2 Standard, 3.0.2 Professional, 3.0.2 Enterprise, 3.0.3 Standard, 3.0.3 Professional, 3.0.3 Enterprise, 3.2 Pro, 3.2 Enterprise, 3.1.1, 3.3, 3.1.1 Professional, 3.1.1 Enterprise, 3.2 Beta, 3.2 Beta Professional, 3.2 Beta Enterprise, 3.3 Pro, 3.3 Enterprise, 3.2.1, 3.2.1 Pro, 3.2.1 Enterprise, 3.2.2, 3.2.2 Pro, 3.2.2 Enterprise, 3.2.3, 3.2.3 Pro, 3.2.3 Enterprise, 3.3 Beta1, 3.3 Beta1 Professional, 3.3 Beta1 Enterprise, 3.4, 3.4 Pro, 3.4 Enterprise, 3.3.1, 3.3.1 Pro, 3.3.1 Enterprise, 3.3.2, 3.3.2 Pro, 3.3.2 Enterprise, 3.3.3, 3.3.3 Pro, 3.3.3 Enterprise, 3.5, 3.4 Beta1 Enterprise , 3.4 Beta1 Pro, 3.4 Beta 1, 3.4.1, 3.5 Pro, 3.5 Enterprise, 3.4.2, 3.4.1 Pro, 3.4.1 Enterprise, 3.4.2 Pro, 3.4.2 Enterprise, 3.4.3, 3.4.3 Pro, 3.4.3 Enterprise, 3.6, 3.5.1, 3.5.1 Pro, 3.5.1 Enterprise, 3.6 Professional, 3.6 Enterprise, 3.5.2, 3.5.3, 3.5.2 Professional, 3.5.2 Enterprise, 3.5.3 Professional, 3.5.3 Enterprise, 3.7, 3.7 Professional, 3.7 Enterprise, 3.6.1, 3.6.2, 3.6.1 Professional, 3.6.1 Enterprise, 3.6.2 Professional, 3.6.2 Enterprise, 3.6.3, 3.8, 3.8 Professional, 3.8 Enterprise, 3.6.4, 3.6.3 Professional, 3.6.3 Enterprise, 3.6.5, 3.6.4 Enterprise, 3.6.4 Professional, 3.7 Issue Views, 3.7 Beta 1, 3.7 Beta 2 Enterprise, 3.7 Beta 2 , 3.7 Beta 2 Professional, 3.7.1, 3.7.1 Professional, 3.7.1 Enterprise, 3.7.2, 3.7.3, 3.7.2 Professional, 3.7.2 Enterprise, 3.7.4, 3.7.3 Professional, 3.7.3 Enterprise, 3.7.4 Enterprise, 3.7.4 Professional, 3.8.1, 3.8.1 Professional, 3.8.1 Enterprise, 3.9
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Andreas Knecht [Atlassian] and Joop
Since last comment: 58 weeks, 5 days ago
Resolution Date: 28/Mar/07 07:55 PM
Labels:


 Description  « Hide
The feature we acquire is to independently export and import Jira configuration (e.g. workflows, screens, permissions) separate from the data (the issues). For instance when running Jira Professional in a test- and in a production environment, both activated with the same workflow. It would be nice if changes are made to the workflow in the test environment, to later "apply" these changes to the workflow in the production environment by exporting and importing the workflow including all its dependencies (e.g. statuses, transition screens, etc).

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andreas Knecht [Atlassian] - 28/Mar/07 07:55 PM
There's already several issues open about this problem. Please voice your opinions there and register your votes. This will increase the likelihood that this feature will be implemented.