Story #11250

[Workbench] Better user-facing terms for container states

Added by Peter Amstutz 16 days ago. Updated 16 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Story points-
Velocity based estimate-

Description

  • When a container is in the slurm queue, its state is displayed as "Locked". This is confusing to users who don't associate "Locked" with "will run in the future".

Instead of "Locked" suggest either "Queued" or Pending".

  • When a container is Queued and has priority 0, it is displayed as "Ready" state. While technically it could enabled to run by adjusting the priority, this most often occurs when a user pushed the cancel button on a container that was in the Queued or Locked state.

Instead of "Ready" suggest "Cancelled" or "Stopped".


Related issues

Duplicated by Arvados - Bug #11186: Priority 0 state shouldn't be labeled "Ready" Duplicate

History

#1 Updated by Peter Amstutz 16 days ago

  • Description updated (diff)

#2 Updated by Peter Amstutz 16 days ago

  • Subject changed from [Workbench] Display "Pending" instead of "Locked" to [Workbench] Better user-facing terms for container states

#3 Updated by Peter Amstutz 16 days ago

  • Description updated (diff)

Also available in: Atom PDF