I have two JIRA projects for the same client (one for marketing and the other for development). I want to know if it the best way is to bulk import the issues from one project to the other, and what are the consequences of doing this (eg. a change in the issue numbers, problems with attached files, etc).
Hi Melanie,There are multiple consequences and a few are:
Question: Are you planning to move all the issues from one to other or only some of them in bulk? What is your goal?
I have been through the path and I would suggest to use Bulk Clone to clone the issues rather moving the issues. You will have to analyze the workflows on both source and target projects to understand how many transitions you will have to go through and create a plan for doing the exercise.
Thank you for answering me!
Both projects have the same workflow, scheme and default assignee, so that won't be a big problem.
We have one project that's only for the marketing issues of the client and the other one that is for everything else. The idea is to move all the issues (almost 400) from the marketing project to the other one and only have one project for each client. But I wasn't sure what the consequences were, so before doing it I wanted to do some research.
Suggestions: Collect statistics on number of issues by component, issue type, and status. Plan to disable webcast and outgoing e-mails, then do the bulk clone and required updates, then enable webcast and outgoing e-mails. I have done it for 36K+ issues without any exception. If you need further help, I can be contacted.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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