You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have two projects that were created using the "Create with shared configuration" option, however, some of the shared components are causing reporting conflicts for our users. We would like to convert the shared components to individual project components without having to recreate the projects. Is this possible?
Yes, copy the shared schemes to new names, then associate the new ones with the projects you want to split off, using the project admin sections for those projects.
(Note that I've used the word "schemes" instead of "components" here, as JIRA "components" means something very specific, and they are items that are not shared by projects)
Hi Nic! Thanks for the swift reply. In this case, the issue I am seeing is not with the project permissions schemes but the global and "Project Specific" components.
One of our users created a project (Project A) and definied custom components for that project, then created a second (Project B) project using the "Create with shared configuration" option. We have two components that were created for Project A, Agents and Culture. Project B has inherited these components from Project A. When one of these components is updated in either Project A or B, those components are modified in the other project as well.
This is skewing reporting and bug fix data.
I know how to import/export/modify project permission schemes, but I'm not sure if that is going to provide me with the solution I'm looking for. I would like to (if possible) prevent Project B from inheriting anything from Project A without having to recreat the projects.