Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting parent step does not prompt deletion confirmation/warning for child steps #4617

Closed
reecewalsh opened this issue Jun 1, 2018 · 2 comments

Comments

@reecewalsh
Copy link

commented Jun 1, 2018

Octopus Version:

Tested and replicated in Octopus version 2018.5.6

Issue:

When selecting the option to delete a single step within the deployment process, a confirmation appears to confirm deletion of the step.

When deleting the parent step container, however, the parent and child steps are deleted without confirmation.

Replication Steps:

  1. Create a new Project

  2. Create a two steps within the deployment process (i.e. Deploy a Package/Run a Script)

  3. Add a Child step to one of these steps to create the parent container.

  4. When deleting the stand-alone step, you are prompted with the following dialog;

image

  1. When deleting the parent step container, however, the step is instantly deleted alongside the child steps.

Source:

https://secure.helpscout.net/conversation/591583143/27613?folderId=1661945

@mayuanyang mayuanyang closed this Jun 4, 2018
@octoreleasebot octoreleasebot added this to the 2018.5.8 milestone Jun 4, 2018
@octoreleasebot

This comment has been minimized.

Copy link

commented Jun 4, 2018

Release Note: Fix a bug where confirm dialog is missing when deleting a parent step from the deployment process

@benPearce1 benPearce1 modified the milestones: 2018.5.8, 2018.6.0 Jun 6, 2018
@lock

This comment has been minimized.

Copy link

commented Nov 23, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot unassigned mayuanyang Nov 23, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants
You can’t perform that action at this time.