We’re working on building a huge Project for our clients based on their requirement in JIRA lower environment.
Once the testing is completed, it is required to migrate the entire project to the higher(Production) environment.
We could oversee a lot of Manual potential that needs to be in place to achieve the production move in the conventional method by replicating all the steps done in lower environment. Also, the other thread is on ACCURACY, since lot of manual work is involved.
Please help us by suggesting any workaround for the Production migration to avoid manual work and to achieve accuracy.
Please consider this as high priority, since we’re facing a short deadline.
Thanks for the extended support,
If it is only a single project migration from, we can use third party plugins to do the job mentioned here
Other way of doing that is to (i would prefer doing it via plugin as mentioned above)
- Create Project configurations like Components, Releases, Schemes using REST API's
- Export Jira issues with required fields as csv from staging.
- Import Jira issues on to Production after making all Project Configuration ready before hand.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs