"Assign to me" button for manual intervention step in child-project doesn't assign the task.

[danefalvo]

Prerequisites

• I have verified the problem exists in the latest version
• I have searched open and closed issues to make sure it isn't already reported
• I have written a descriptive issue title
• I have linked the original source of this report
• I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

If your on the task summary page of a project that is currently being deployed and a child-project reaches a manual intervention step, you are prompted with an alert message - in which you can assign the manual intervention step to yourself - by clicking the "Assign to me" button. Clicking the button changes a message on the page from: "Assigned to: No one" to "Assigned to: you".

However, this button doesn't actually assign the manual intervention step to anyone. If you navigate to the manual intervention task - you are still prompted to assign the step to someone.

What I expected to happen

Clicking on "Assign to me" should assign the manual intervention step to me.

Steps to reproduce

1. Create two projects. Project 1 should have the step "Deploy a release". Project 2 should be the release that it deploys and it should contain a "Manual intervention step"
2. Deploy Project 1. Stay on the Task Summary screen as Project 1 deploys and calls Project 2.
3. When Project 2 reaches the manual intervention step, you will be prompted to assign the Manual Intervention step to yourself.
4. Assign the manual intervention step, so that it now says "Assigned to: you".
5. Open "Tasks" and click on the Child Project Manual intervention step. You will see that the task is not assigned to anyone.

Screen capture

Affected versions

Tested on latest version of Octopus Cloud. 2020.3.1

Added Edit

After Triaging another issue - I have discovered that the same symptoms appear when dealing with a triggered guided failure within a child step.

Links

https://secure.helpscout.net/conversation/1229998029/67723?folderId=3767284

[mcasperson]

We have flagged this as an issue with product, but at this point we do not have capacity to assign an engineer to resolve the issue. We'll keep the issue open, but unfortunately we can not provide any guidance as to when it will be resolved.

[droyad]

This is because the interruptions that show up are the interruptions on the parent deployment not the interruptions that occur on the child. These interruptions are created to pause the parent until the child ones are resolved. These interruptions are then auto-resolved.

We probably shouldn't show this UI on the parent at all.

[octoreleasebot]

Release Note: Interruptions in child deployments can now be actioned from the parent deployment task log

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.6432
2024.3+	all releases