@iq test free I completely agree that displaying pipeline parameters in the UI is essential for clarity. Without visibility into these parameters, it becomes challenging to determine the specific actions of each job, such as whether it’s compiling, testing, or deploying. Adding a clear representation of these parameters would greatly enhance our workflow management. Also, I support the suggestion to add a "User Interface" category to the "Ideas" section for better organization.

I just started writing up a new feature request for this then found this one already here for nearly 5 years 😭 (I can't understand why such a simple and obviously necessary feature hasn't been implemented yet...?)

If I define pipeline parameters in the config then when I "Trigger Pipeline" there is a UI for entering param values.

But AFAICT there is no way to go back and see what param values were chosen on a previously triggered workflow, e.g. https://app.circleci.com/pipelines/github/infomediacode/superservice-analytics/4318/workflows/a9b1c6a9-5a3f-497e-8860-7bac0124e4ac

I would like to be able to see the param values on:

Would change my life. I have to do hacks by echoing the parameters in a step.

This feature would greatly improve build auditability, i.e. knowing for each triggered build, what parameter values were used. Similarly it would assist in debugging.

I was expecting to find something similar to how Jenkins does this: https://plugins.jenkins.io/show-build-parameters/

Yes. It would also be used to expose them via the API.

I agree having a nicer, summarized view of all the pipeline parameters would be a useful feature.

But in the interim, you should be able to view what the value of your parameters resolved to by going to a workflow or job details page -> top right ellipses -> Configuration File -> Compiled. We show the original source configuration you committed as well as what the processing "compiles" or resolves to.