
| Key: |
JRA-3819
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Richard THIBAULT
|
| Votes: |
3
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
JIRA
Created: 26/May/04 04:32 PM
Updated: 27/Jun/07 05:39 PM
|
|
| Component/s: |
Import / Export
|
| Affects Version/s: |
2.6.1 Enterprise
|
| Fix Version/s: |
None
|
|
|
In large companies, we need to have a testing environment and a production environment to prevent production probems. The JIRA testing environment is used to test parameters changes (change in schemes, change in the workflow, change in a global parameter).
After the tests have been done, we want to apply the change in the production environment. We cannot do that with JIRA since we cannot export and import only the parameters.
To do that we should be able to export and import everything except issues, projects and users/groups.
A coherence control should be performed by JIRA during the importing phase. Some choices should be proposed to the users if some incoherences were detected.
|
|
Description
|
In large companies, we need to have a testing environment and a production environment to prevent production probems. The JIRA testing environment is used to test parameters changes (change in schemes, change in the workflow, change in a global parameter).
After the tests have been done, we want to apply the change in the production environment. We cannot do that with JIRA since we cannot export and import only the parameters.
To do that we should be able to export and import everything except issues, projects and users/groups.
A coherence control should be performed by JIRA during the importing phase. Some choices should be proposed to the users if some incoherences were detected. |
Show » |
|