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

UI glitches out when reordering newly created lifecycle phases #6647

Open
5 tasks done
calverp opened this issue Oct 27, 2020 · 2 comments
Open
5 tasks done

UI glitches out when reordering newly created lifecycle phases #6647

calverp opened this issue Oct 27, 2020 · 2 comments
Labels
area/core feature/lifecycle kind/bug This issue represents a verified problem we are committed to solving

Comments

@calverp
Copy link

calverp commented Oct 27, 2020

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.

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

When creating a new lifecycle phase and re-ordering the phases the list will multiply.

What I expected to happen

The phases should not reproduce

Steps to reproduce

  • Save a lifecycle with at least 2 phases
  • Edit the lifecycle and add at least 2 new phases
  • Select Re-order phases and drag any phase around
  • Observe the phases multiply
  • If you exit the re-order and click the button again, a red error appears. Clearing the browser cache (ctrl-f5) removes the error

Screen capture

image
image

Affected versions

Octopus Server: 2020.4.2

Workarounds

Saving the lifecycle after adding the new phase(s) and then going back in to re-order them seems to prevent this issue.

Links

Internal Link

@calverp calverp added the kind/bug This issue represents a verified problem we are committed to solving label Oct 27, 2020
@calverp
Copy link
Author

calverp commented Oct 27, 2020

@mcasperson mcasperson added the product/noqrfcapacity Do not use this label anymore label Oct 27, 2020
@mcasperson
Copy link

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.

@kengel100 kengel100 added area/core feature/lifecycle and removed product/noqrfcapacity Do not use this label anymore labels Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core feature/lifecycle kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants