[Feature Request] UX Improvements

[rifelpet]

Is your feature request related to a problem? Please describe.

I've collected some notes on frustrations while using the Temporal UI, I hope this is helpful.

In general I use the UI when getting insight into a currently-running or recently-failed workflow execution. I want to easily see the current status of a running workflow or where an execution failed and what its inputs were. This includes digging into child workflow executions when relevant.

Frustrations:

• The /history/compact view of a workflow execution has no links to child workflow executions. In the events table where a row's event type is a Child Workflow, there is a StartChildWorkflowExecutionInitiated span underlined and highlighted like a hyperlink but clicking it doesn't do anything

• /history/compact shows inputs of child workflow executions and activities, but not outputs

  

• /history/compact doesn't include any error information when a child workflow fails or times out. There are red rows in the /history/feed table but not /history/compact

• In order to click into child workflow executions, I need to use /history/feed. The
  ChildWorkflowExecutionStarted event rows have a link to the child workflow execution, but when expanding the event row that link dissappears. I have to click the Workflow tab within the row to get those links back

  

• For workflow executions with a deep nesting of child workflows, having to track down the inputs, outputs, and statuses of the deeply-nested child workflows takes an inordinate amount of mouse clicks

• On any of the /history views for a workflow execution, the workflow's own timeout settings are not visible

Describe the solution you'd like

Reducing the # of mouse clicks required to navigate through all of the above information would be an immense improvement.

I'm imagining a single page that shows events from the current workflow execution and all child workflow executions (recursively) their workflow/activity types, task queues, inputs, outputs, and statuses (any timeouts, cancellations, failures, etc.). That would be incredibly beneficial.

This would allow me to easily navigate to exactly what failed and understand the context around the failure.

Describe alternatives you've considered

Additional context

[Alex-Tideman]

@rifelpet thanks for the great feedback! I'll work with @canvanooo to see how we can incorporate these ideas.

[Hades32]

Oh yes! Even just making the child workflow ID clickable would be a start