forcedotcom
Manually choose Work Items to include in Bundle
In the Bundling Stage, allow admins to choose which Work Items to include in a bundle.
I would love this one. Right now we choose not to use Bundles and hence gave up on the versioning and validation against production (at least through DOC, we still do it outside)
Hi @OakyRob and @cnwork - Thank you for the feature request. Just to confirm, are you looking for the possibility to choose which (individual) work items to promote to the next stage in a bundling stage, rather than promote the entire stage? If yes, could you share a little bit about your use case and how it will help you?
Hey @GilsonCanario, sorry for the late reply. Since my comment here we had to drop using the DOC for other limitation for which we couldn't find any workaround. However, because I spent quite a lot of time investigating and using it I can add my comments related to this. Our pipeline has only INT -> UAT -> Prod. Let's say that our UAT is the bundling stage. When moving WIs from INT to UAT, they will ALL be sent to be part of the bundle in UAT. That bundle will then be moved to Prod with all the WIs in it. Basically there's no way for a ticket to go past the UAT stage without getting into that same bundle. For us, the best would be if the bundle would be a choice not an enforcement. You can send WIs to the next stage to be part of a bundle or not be part of a bundle. Maybe having multiple possible bundles into the same stage could also be beneficial. But anyway, allowing admins or release managers to select if a ticket should be part of a bundle or not would be a great benefit.
Since we are talking about bundles, I also wanted to bring to attention the case of combining WIs. In the current implementation, when having multiple WIs at the same time at different stages of the pipeline, DOC is sometimes giving the option to combine (for certain conflicts of the same files being changed in more than one WI) when moving to the next stage. That is fine, but sometimes we don't want to move to the next stage some of the WIs that are suggested by DOC to be combined. But at the moment is all or nothing. It would be great to allow users to choose which WIs to combine instead of forcing all of them. An example of multiple occasions when this would have been helpful, is when a developer has moved changes to INT and realized that he missed some changes and would need to create a new WI to add to the original one, OR when the WI made it to UAT stage and from tests, an issue was noticed and needed some extra changes which again would come as a new WI. In these 2 scenarios, it would help to say that once I moved the second WI to the same stage as the previous one, I can now combine them into what originally was supposed to be only one WI anyway. It would greatly reduce the amount of WI that are sitting inside the pipeline and would need to be visualized and sorted through by release managers. Thanks for the attention!
This is really needed. Two different teams should be able to validate and deploy their releases separately as separate bundles rather than entire stage deployment as single bundle. How to segregate work items as per release in bundling stage? @GilsonCanario
