Projects - Demotion of Just One Source?

CathyC · Unread post by **CathyC** » 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

stowejs · Unread post by **stowejs** » February 10th, 2022, 6:15 pm

An additional ask to this would be the ability to move a source from QA to DV without undoing the changes in QA so testing can continue while the issue is fixed.

JefferyD · Unread post by **JefferyD** » February 10th, 2022, 6:59 pm

To add to this, I would also like a way to demote a specific subset of sources in a project to DV while keeping the project itself in QA. The purpose being to allow changes and fixes to existing sources without reverting the sources in QA so that any testing can resume. This would also have the added benefit of reducing the time waiting for demotions and promotions if some sources don't need to be moved.

Possible Implementation Example

Click "Demote" and have a window pop-up with "Demote Whole Project" and "Demote Specific Sources"
"Demote Whole Project" functions like current demotion while "Demote Specific Sources" instead asks the developer to select from the list of sources to demote
After selecting the list of sources, the developer then selects 1 or multiple tasks attached to the project which get updated to "In Progress" status
The selected sources then become editable in DV without reverting any changes currently in QA
Once the changes have been made, the tasks are set to "Ready For Testing" by the developer
Finally, the developer promotes the changes to QA to be tested without requiring the whole project to be retested

CathyC · Unread post by **CathyC** » December 21st, 2022, 4:08 pm

We talked about this again today. Earlier this week there was a revision applied that meant we couldnt demote from QA to DV. There was a workaround that Justin did where he demoted the source Jeff needed to DV, but the changes remained in QA.

Need project to remain in QA, but the source can be demoted (soft demote)
This soft demote would not need to copy from PD to revert QA at all

When trying to promote from QA to PD, it should check if you have any sources soft demoted. It would say "you cannot promote this until all sources within the project are in QA. You have sources in DV currently"

Discussed with Suman, he will review

CathyC · Unread post by **CathyC** » May 9th, 2023, 11:18 am

Task #11062 was created to track this discussion

K-Rise Systems