search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Unable to promote / Set Never work item that was manually merged into repo #252

Open SporcleHans opened 1 year ago

SporcleHans commented 1 year ago

Describe the bug Hello,

I had a work item that I accidentally manually merged via github instead through the devops center. I used the built in github tool to roll back the merge, but now the work item is stuck "in review", but it doesn't show up in the pipeline to promote. On the work item itself it just says "Merged Externally" and that I can't make any edits to the work item. It's blocking my developer from being able to sync with the next environment because devops center believes the work item is still in review.

To Reproduce Steps to reproduce the behavior:

  1. Manually merge a pull request from a work item
  2. roll back the pull request

Expected behavior Being able to promote the work item, or set it to "never"

franciscoperezsammartino commented 1 year ago

Hi SporcleHans, DevOps Center does not support RollBack an external merge. Still it should show the Work Item in the Approved column to be deployed (because it was already merged) into the next stage.

My suggestion would be abandon that Work Item and create a new one to keep on your development. As you said that you rollback the changes, the pipeline stage should not have any changes from the merged work item.

SporcleHans commented 1 year ago

Thanks that is what we did, but unfortunately the main issue is that it will not let us sync the sandbox with the next development stage as it says that the github merged work item is still "In Progress"

franciscoperezsammartino commented 1 year ago

Okey, yes thats a problem. I will try to look at some possibilities for a workaround, but probably it will very involved. If you can keep working with other environments then that would be good.

Sorry for this.

sdavis-AWP commented 1 year ago

^^ This. If a WI fails to deploy in a downstream environment after initial deployment from dev environment, there's no way to roll back the work item, change to never, or even delete it(without manually deleting the records). It stays stuck in the pipeline. Then if you create a new work item with the same metadata/source members, it will be blocked from deployment due to dependency on the failed work item.