Hello,
Is there a way to copy a project including schemas and new fields, automations and everything that was set up for the project in the TEST environment to the production environment? I would like to point out that we are working in an environment disconnected from the Internet.
I would appreciate your answer,
Natali Daniel
Hi @Natali Welcome to the Atlassian Community
Sadly, a 1-to-1 copy is not possible. The ID's for quite the number of entities could coincide with ID's of already present entities (project ID, custom field ID's, Automation rule ID's etc.). Also the ID's of relative static entities might not coincide (issue type IDs, workflow ID's) etc.
You would need to export and import the project. But do not expect custom fields to be generated automatically (and even upon manual insertion: have the same reference number).
Kind regards,
Dick
Thank you very much,
I wanted to ask assuming that the new fields were also created in the production cycle, so the schemas of the screens and the WORKFLOW will be replicated by the EXPOT-IMPORT project?
JIRA does not know how to take all the data and give new IDs to WORKFLOW, fields, etc.?
I would like to know if there is perhaps an external tool that can do this?
Regards,
Natali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the custom fields were created, it does not guarantee that the numeric value part in their ID is the same. As custom fields are used in automations by their ID, you're bound to have errors if you transfer your automation script 1-on-1. I've been into that alley myself...
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The biggest tip would be to only put test data on a test environment.
The second tip would be
If there's more than 1000 issues, you need to do this multiple times (select first issues with key < 1000 then consequently key >=1000 and key <2000 etc. until you have exported all issues)
Thirdly, you need to adapt automations to use the correct custom fields.
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.