PipelineRun details page design updates

[AlanGreene]

This issue will be used to track work on the new PipelineRun details page design updates. For now it serves as a central reference point for some of the existing related issues.

Many of these would greatly benefit from design input as the current design cannot easily accommodate the additional content without negatively impacting on user experience. One of the overarching themes through many of these items is:

• improving information hierarchy, much useful content buried in multi-level deep tabs

Other items (in no particular order):

• [ ] diagram / visualisation: https://github.com/tektoncd/dashboard/issues/675
• [ ] YAML view: https://github.com/tektoncd/dashboard/issues/762
• [x] sidecars: https://github.com/tektoncd/dashboard/issues/972
• [x] labels: https://github.com/tektoncd/dashboard/issues/1181
• [x] retries: https://github.com/tektoncd/dashboard/issues/1445
• [x] run duration https://github.com/tektoncd/dashboard/pull/4293
• [ ] params and results: https://github.com/tektoncd/dashboard/issues/1570
• [x] actions: https://github.com/tektoncd/dashboard/issues/2261
• [ ] when expressions: https://github.com/tektoncd/dashboard/issues/2293 and https://github.com/tektoncd/dashboard/issues/1445
• [ ] scrolling / user interaction improvements
  • [x] select a task / step near the bottom of a long task list, browser doesn't automatically scroll back to top to see the tab headings
    • ✅ similarly, when loading a failed PipelineRun, although we automatically select the first failed step, it may be displayed
    • TaskRun tabs and the main content are now independently scrollable. When there are many tasks they can be scrolled within the viewport.
    • Also, the tabs are sticky to the top of the page so they're always visible even if scrolling to bottom of long logs. below the fold in the task tree
  • [x] we need a better way to display the list of tasks, some options we've discussed in the past:
    • use the DAG visualisation
      • still on the roadmap: https://github.com/tektoncd/dashboard/issues/675
    • ~~more condensed tree view~~
      • switched to vertical tabs for tasks, steps moved to right content pane
    • ~~dropdown~~
      • need to provide glanceable status (inc. durations)
    • ?
  • [x] https://github.com/tektoncd/dashboard/issues/3327
  • [ ] scroll to top/bottom
    • we had this previously when there was only 1 log container per page
    • should it scroll to top/bottom of page, or only of current log container?
  • [ ] auto-scroll to bottom on update
    • we need to be careful with this one as logs may become available out of order and we don't want to jump back to something the user has already scrolled past. We need to ensure there's only 1 'active' log container considered at a time for this
• [ ] https://github.com/tektoncd/dashboard/issues/3443
• [ ] custom tasks https://github.com/tektoncd/dashboard/issues/1970, e.g. task-loops, pipelines-in-pipelines
• [x] TEP-0090: Matrix https://github.com/tektoncd/dashboard/issues/2410
  • initial support delivered in https://github.com/tektoncd/dashboard/pull/3081
  • additional work required to display matrix.include.displayName and also support for https://github.com/tektoncd/pipeline/issues/7200 and/or https://github.com/tektoncd/pipeline/issues/7082
• [ ] audit status icon use (also related to #2293)
• [x] consistent display of duration https://github.com/tektoncd/dashboard/issues/3767
• [x] pipeline task display name https://github.com/tektoncd/dashboard/issues/2792
• [ ] pipeline task description (related to display name which was added in 2792)
• [ ] consider markdown support for display name / description https://github.com/tektoncd/dashboard/issues/3804
• [ ] log viewer improvements
  • [ ] https://github.com/tektoncd/dashboard/issues/3443
  • [ ] restore per-log "open in new window" / download options in toolbar

These are some of the issues currently being considered as part of the design effort.

There's also quite a bit of overlap here with the TaskRun details, so many of these changes will benefit that page too.

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[AlanGreene]

This is still very much something that is planned. Freezing so it doesn't get automatically closed. /lifecycle frozen