Feature Request: Allow descriptions to be added to V2 Overrides
long-term
V
Venetian yellow Limpet
We have a lot of overrides that have been migrated to V2 (global environment, service specific, etc.)
It would be nice if we could add a description when creating a new variable in the Override section. Right now the only fields allowed are the variable name and value.
Could we add a new field that allows a description to be set
Log In
Autopilot
Merged in a post:
Feature Request - Pipeline variable description
E
Elderly Quail
Requesting for a feature to have description to pipeline variables on Pipelines, if possible. This will greatly help give context to users especially on runtime inputs without looking at docs on a separate location.
Autopilot
Merged in a post:
To Have Stage/Pipeline Variables Description Length To Be Visible Entirely
J
Jade green Wildfowl
Can we get the variable description to have couple more lines before it truncates? Currently it is truncating too early before showing the complete URL of the user guide and also to make the confluence user guide URL be clickable so that it opens in a new page when the user clicks on it.
Autopilot
Merged in a post:
Display description on input variables
S
Sole Chimpanzee
Please allow the display of descriptions on input variables. Currently, there is a little icon with a hover hitbox that shows the description value... this is not intuitive and is not accessibility compliant. The descriptions we provide for inputs should be visible when starting a pipeline. This used to be displayed this way and is now replaced with a useless hover hitbox.
Rohan Gupta
marked this post as
long-term
This is a fair requirement, we can add description to the override object. Adding this to our long term backlog.
Autopilot
Merged in a post:
Shell Script Output Descriptions
G
Ginger Dove
For users to be able to better understand what a shell script output's variables are for we think it would be beneficial for them to have an optional description.
Example: Have a shell script output yaml that is intended for a helm step later on so put a description for that
Have a shell script output an s3 artifact path and have it be used in a future CloudFormation stack so put a description for that.
We like that stage variables can have descriptions for inputs to users informed of where their values might be used but there wasnt any ability for doing that with shell scripts inputs/outputs
Autopilot
Merged in a post:
Option to display description for Pipeline Input variables instead of the user having to hover over description icon
H
Historic Mole
Currently when triggering the pipeline and entering the values through an input set, the variable description of the pipeline/template/stage variables are behind the description icon and the user has to manually hover the icon to view the description. This request is to see, if we can have an Option to display description for Pipeline Input variables instead of the user having to hover over description icon. The service input variables display it without the display icon. Having an uniform experience for both pipeline and service variables will help the user experience
S
Sole Chimpanzee
I would still like this feature. We auto-generate pipelines for thousands of pipelines and having visible descriptions makes it user-friendly when running a pipeline that you are unfamiliar with. This feature would also help teams that share pipelines with non-team members communicate what the inputs are. The hover is NOT obvious and leads to confusion. This has been a support nightmare for our internal devops teams.
I am not sure that the product people making these decisions use the product on a daily basis like we do.
Sudarshan Purohit
Hi Jade green Wildfowl, could you point us to which screen you're seeing the issue in? On forms we've generally kept the description as a popover in order to have space for the variable name and input fields.
Sudarshan Purohit
Hi Sole Chimpanzee, this was a conscious decision taken to preserve space for the variable names and input fields. Because the same Form is likely to be used multiple times for running the Pipeline, we assume the users become familiar with the variables and the expected values. Longer variable names and values are expected, and a large description field reduces space for them.
We will revisit this in future as new use cases emerge, but for now, we will not be taking up this request.
O
Orchid Piranha
Sudarshan Purohit I maybe missing something, but we don't see ANY description icon while editing the overrides via UI. Your comment says large description field is not possible, can we just have a description icon which can display text when users hovers over it ?