RFC: New task detail page

RFC: New task detail page

Hi, I was playing around trying to fix some small issues on the Task detail page, and I accidentally redesigned the whole thing (without talking to you). So here I am asking for:

  1. Feedback for the proposed design (e.g., combining tabs, naming)
  2. Any current pain points that come to your mind
  3. Are you even checking tabs or are you going directly to the Dynflow console
  4. When do you use locks?
  5. Is it possible to create human-readable error notifications?
  6. What do you normally do on this page?

or any of these.

Current state

Proposal

  • Combining Running steps and the Errors tab
  • Using a short inline alert to display problematic issues
  • The progress bar was displayed just during the progress
  • Some buttons are hidden in the kebab
  • More informative empty states
  • More informative Locks tab
  • PF5

Proposed designs

Bear in mind, this is not pixel-perfect; it’s a draft. Everything can be changed, microcopy still needs review. Dummy data, state terminology is not precise (I am aware). I am not sure about primary, secondary buttons - so u can see multiple alternatives here.

Running

Suspended steps

(I guess more info needed here about the steps)

Success

Stopped

Stopped collapsed

Error

Locks

Locks populated

Locks - empty state

3 Likes

On this picture, is auto reload on or off? I would assume it is off, but I’m not sure.

I know this is personal preference, but the fields like state, label and so one were easier to read in the more table-like layout of the old design.

Also, the “Start at” field is a relatively important one for things which were scheduled for the future.

The “Temporarily suspended step(s)” makes it sound a bit as if it is an outcome of some user action while in reality (and in most cases) it is just the task waiting for some external action to finish. With that being said, I don’t really have any suggestions that would read better.

In theory, there can be multiple warnings, errors, inputs, outputs, exceptions and backtraces at the same time for example if multiple concurrent steps of a single task failed. How would this be displayed then?

Afaik there is no documentation on resource locking as that is a mostly internal thing that the user has little to no options to affect.

What’s in the raw tab?

1 Like

This is a from a very quick glance, and may be biased by looking at the old page for years, but I agree that the state and such on the old page feel easier to read quickly.

Otherwise I’m liking what I’m seeing!

The result and state values both indicate the status of a task so it’d be good to retain the result field for task details.

On the success screen I like seeing the 100% complete green progress bar on the old UI. It tells you immediately that all is good. Same for the red progress bar for errors.

Also, there is the new dependency tab[1] that was introduced last week-ish.

[1] - Fixes #39130 - correct task dependency names by ianballou · Pull Request #796 · theforeman/foreman-tasks · GitHub

If Revisiting Action Cable for notifications, 6 years later gets traction, perhaps it could also be applied here. Then the whole choice around auto-reloading won’t be needed any more and it could “just work.”