Skip to content

Conversation

@Arnei
Copy link
Member

@Arnei Arnei commented Aug 7, 2025

"Time in queue" is one of the variables shown for worklow operation details. However, the name is misleading, as this does not refer to the time the operation (or the job representing it) was waiting before starting. Instead, it represents the time all the jobs the operation has spawned were waiting.
Which is why "time in queue" so often has the value "0ms", as many workflow operations simply don't spawn an jobs.

This patch attempts to make this more clear by changing "time in queue" to "total subjobs time in queue". Suggestions are welcome.

"Time in queue" is one of the variables shown for worklow operation
details. However, the name is misleading, as this does not
refer to the time the operation (or the job representing it) was waiting
before starting. Instead, it represents the time all the jobs the
operation has spawned were waiting.
Which is why "time in queue" so often has the value "0ms", as many
workflow operations simply don't spawn an jobs.

This patch attempts to make this more clear by changing "time in
queue" to "total subjobs time in queue". Suggestions are welcome.
@Arnei Arnei added the type:visual-clarity Improves UI readability label Aug 7, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Aug 7, 2025

Use docker or podman to test this pull request locally.

Run test server using develop.opencast.org as backend:

podman run --rm -it -p 127.0.0.1:3000:3000 ghcr.io/opencast/opencast-admin-interface:pr-1396

Specify a different backend like stable.opencast.org:

podman run --rm -it -p 127.0.0.1:3000:3000 -e PROXY_TARGET=https://stable.opencast.org ghcr.io/opencast/opencast-admin-interface:pr-1396

It may take a few seconds for the interface to spin up.
It will then be available at http://127.0.0.1:3000.
For more options you can pass on to the proxy, take a look at the README.md.

@gregorydlogan
Copy link
Member

While I applaud the idea, I'm wondering if that's going to be too long to fit comfortably in the header of a table. Could we change the text to Total time in queue, with a hover-over explaining things? I'm assuming that's a no-no accessibility wise?

@Arnei
Copy link
Member Author

Arnei commented Sep 1, 2025

I think it kinda still fits, but fair enough, we don't need to cut it close (especially considering translations).

Hover text is less of an accessibility thing and more of a UX thing. We can always add screen reader text and what not to accommodate accessibility, but expecting users to hover an element they have no innate reason to hover over (unlike e.g. a button) is unintuitive for many users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:visual-clarity Improves UI readability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants