Show task parameters in the UI, similar to how flow parameters are shown

[ALMerrill]

First check

• [X] I added a descriptive title to this issue.
• [X] I used the GitHub search to find a similar request and didn't find it.
• [X] I searched the Prefect documentation for this feature.

Prefect Version

2.x

Describe the current behavior

As stated in the UI, “Task inputs show parameter keys and can also show task run relationships.” So you can currently see the names/keys of the parameters to a task, and which task they came from if they are the output of a previous task, but you cannot see the values. For flows, under the Parameters tab, you can see the names and values of the parameters. Example of what is shown for flows:

{
  “param1”: “value1”,
  “param2”: false
}

Describe the proposed behavior

It would be nice if you had a parameters tab for tasks as well, to easily see the passing of values through a workflow.

Along with this, and I can put this into a new issue if that would work better, it would be nice if the outputs of tasks and flows could be visualized in a similar manner, at least when they are simple types like string, int, bool, maybe dictionaries, etc. or if they have a resolver into a simple type. I just feel that seeing inputs and outputs to each flow, subflow or task would improve the visibility of what’s happening.

Example Use

An example could be that a workflow has an error, and it is difficult to see what the cause of the error is, solely based off of the stack trace. If you’re able to follow the inputs and outputs of the tasks leading up to the task that had the error, this may show what caused the error, if you see an unexpected value for one of the inputs to the breaking task.

Additional context

No response

[zhen0]

Thanks @ALMerrill - we appreciate you taking the time to make this into an issue.

@cicdw - for consideration in future task work 😀

[sgbaird]

xref: https://linen.prefect.io/t/2430432/ohhh-got-it-so-one-flow-kicks-off-multiple-flows-and-we-use- which describes the workarounds:

1. Naming task runs based on inputs (Prefect docs)
2. using prefect.Parameter to display them on the flow run page