Projects - Demotion of Just One Source?
Posted: February 10th, 2022, 5:22 pm
I have an issue I run into sometimes. Lets say I have 30 sources all checked out for a fairly large release coming in a few weeks. The UAT on this has taken a few months, so I am in a code freeze and don't want to introduce any risk at this point by making changes. A PD bug is found, but the fix must be made in one of the 30 sources. I know this involves taking the one source, making the fix in DV and disconnecting the project change that cant go to PD yet, then promoting that all the way through to PD to fix the bug. After that is done, I will check it out again, reconnect the project changes, and return it to the original project in QA waiting for go-live.
The problem: I have to demote the project with all 30 sources to DV in order to move the 1 source out to its own project. Then move the original project back to QA. During this time, I am touching all 30 sources and introducing risk. Also, during the demotion/promotion step I am breaking QA by removing this feature and then adding it back. Anyone testing the QA site at this point will raise issues that the change is not working as expected.
Proposed fix: I would like to be able to move the 1 source to a new project from QA. This leaves the 29 sources untouched and reduces the risk while I do the necessary fix for PD
The problem: I have to demote the project with all 30 sources to DV in order to move the 1 source out to its own project. Then move the original project back to QA. During this time, I am touching all 30 sources and introducing risk. Also, during the demotion/promotion step I am breaking QA by removing this feature and then adding it back. Anyone testing the QA site at this point will raise issues that the change is not working as expected.
Proposed fix: I would like to be able to move the 1 source to a new project from QA. This leaves the 29 sources untouched and reduces the risk while I do the necessary fix for PD