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

Prompted variable in library and project set can duplicate #6657

Open
5 tasks done
calverp opened this issue Nov 4, 2020 · 1 comment
Open
5 tasks done

Prompted variable in library and project set can duplicate #6657

calverp opened this issue Nov 4, 2020 · 1 comment
Labels
area/core feature/variables kind/bug This issue represents a verified problem we are committed to solving

Comments

@calverp
Copy link

calverp commented Nov 4, 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

If a variable exists in a library variable set and a project variable set and is set to Prompt, it will appear twice on the deploy screen.
The value set in the project variable will still take priority though.

What I expected to happen

Only the project variable should appear on the prompt screen.

Steps to reproduce

  1. Create a variable in a library variable set e.g. "PromptTest"
  2. Set the variable to Prompt
  3. Assign the variable set to a project
  4. Create a variable within the project with the same name e.g. "PromptTest"
  5. Create a release and deploy
  6. Check the prompt variables on deploy screen, "PromptTest" will appear twice

Screen capture

image

Affected versions

Octopus Server: 2020.5.0

Workarounds

This is mainly a UI issue, the behaviour of the variables remain the same i.e. the project variable will override the library variable

Links

https://help.octopus.com/t/variable-override/25917

@calverp calverp added the kind/bug This issue represents a verified problem we are committed to solving label Nov 4, 2020
@adrianhowchin
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.

@adrianhowchin adrianhowchin added the product/noqrfcapacity Do not use this label anymore label Nov 10, 2020
@kengel100 kengel100 added area/core feature/variables 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/variables kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants