We have a production system with a few schemas and the administrator is located in the US.
I am in India and work on modifying existing schemas, develop any plugins required, etc.
How do you handle moving data from a development system to production?
Here is another one. The data that exists in the US cannot be moved to India. How do I move everything other than the projects from the production to the devlopment? I know about the export/import but I am asking if there is a easy solution to bring in all the schemas, etc and none of the issues and projects that exist on the production instance into the development system.
I would also like to hear how some of you are managing your production/development environment to get some ideas.
Thank you
Bhushan
Community moderators have prevented the ability to post new answers.
Hi,
There used to be a plugin called JIRA Workflow Sharing Plugin that made it possible to share workflows between instances. It is now deprecated as it is pre-installed in OnDemand and the functionality will be bundled in JIRA 6 (which can be downloaded as part of EAP) With some tweaks you could actually get it to bring over most of the stuff (i.e. screens)
Check this link: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-workflow-sharing-plugin
Rgrds,
// Svante
Great. What about issue types, field configurations, screens, notifications and everything else? How would you manage moving them from development to production?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I recall the sharing plugin just managed the workflows and the stuff dependent on them.
Issue Types were not imported, but they are easily created in your prod environment and then linked to your newly imported workflows.
Sreens attached to transitions in the workflow are also exported as well as any custom fields fields on the screens that do not exist in your prod environment
To get all custom fields that are created for a specifiic Issue Type/Workflow I tweaked this workflow by adding a "bogus" screen with all relevant custom fields added before the export. This would ensure the custom fields to be created in your prod environment when importing the workflow. Then I removed that screen from the prod environment.
There is another question about this here at Atlassian Answers that may help as well: https://answers.atlassian.com/questions/81151/how-do-i-use-workflow-sharing-and-custom-fields?page=1#95355
Rgrds,
// Svante
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
and another note:
The notification and permission schemes are not exported. They have to be exported in another way or just re-created in the prod environment. They are fairly simple to reproduce, I think!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.