Hello @Melanie Frasier ,
It's possible, but it will take a bit of work and accepting some differences. Steps that you would need to do are:
Note that by moving issues to other projects will change the issue key as well as any additional configurations (workflows, custom fields, etc) if the configurations differ between one project and another. You may be prompted to specify the mapping of statuses from one project to another if the workflows differ, and you'll also want to make sure that custom fields exist in both source and target projects.
Hope this helps
Are those projects Company Managed projects or Team Managed projects or a mix of both?
Are those projects Work Management (a.k.a. Business) projects, Software projects, Service Management projects, or some mix of the three?
Do you have agile boards associated with these projects?
If these are all Company Managed projects and of just one type (Business or Software, or Service Management) do all the projects use the same set of shared Schemes (workflow, notification, permission, field configurations, issue types, etc.)?
You are going to need to analyze the projects to determine how they are the same and how they are different. Simplistically, the projects all need to be of the same type and use identical schemes. If they are identical, then you can Move the issues from their origin projects to a shared project. However, if the original projects had associated agile boards, the history for those boards will be lost as those boards probably use filters based on Projects and the issues will no longer be in the referenced Projects.
If the projects are not of the same type and identically configured, then there will be additional work involved to analyze the differences and figure out to address those.
If you are working with Team Managed projects that adds another layer of complexity.
These are all worthwhile considerations to think through! Good thoughts
It looks like you're new here. Sign in or register to get started.