Pre-populate parameter names in "Run Pipeline" feature | Feature Requests

Pre-populate parameter names in "Run Pipeline" feature

Jenny Miggin

When using the "Run Pipeline" feature, the name of the parameter is currently left blank, and open to incorrect use. It would be useful to pre-populate this with a list of parameters that have been defined within the config file.

November 9, 2021

Nathan

Currently using circle ci for CICD, but still using Jenkins for most other automation tasks specifically because this feature is missing.

Wilfried Goesgens

We at ArangoDB would like to have the complete set of parameters pre-filled with defaults from the

config.yml

with possibly drop downs, so you can choose which params to alter in contrast to the default.

Nathan Fish

Merged in a post:

Dropdown menu for Enum Parameters in Pipeline Trigger

Daniel Bollom

Users would find it easier if the system could identify an enum parameter in the

config.yml

file and display these enum parameters as a dropdown menu, rather than a text box, in the pipeline trigger modal.

This enhancement would streamline the pipeline initiation process, making it more user-friendly. By presenting enum parameters as a dropdown menu, we could reduce potential input errors. Additionally, this change would increase efficiency by saving users' time when triggering pipelines.

August 3, 2023

Nicholas Shaw

Adding upvotes for Agero, even just placeholder text or some sort of informational text that can provided to help the end-user do things the right way would be great

Nawfal Haddi

It’s really needed, It will make using Dashboard easier

Travis Perullo

Adding upvotes for Cisco.

David Castillo

+1 upvote for Penn Gaming who listed this as one of the main reasons for not moving forward with CircleCI as well as lack of visibility into what parameters have been passed into said trigger workflows.

samay simant

A much needed feature.Becomes next to impossible to remember the parameter names when you have heaps of projects to manage.

Diederick van der Heijden

+1 upvote for Outfit7 who have indicated this is a blocker for them

Attila

I am definitely missing this features as well. It would be also nice to see further details as well, maybe the description and the default value of the parameters. This would be a great boost to the productivity. Without this I end up looking up the parameter definitions in the configuration files when I need to use them, which is not a big deal, but this could be avoided with this minor improvement.

Andrew Tremblay

Attila: +1 for including default values.

→