[Workbench] Better user-facing terms for container states
|Assignee:||Radhika Chippada||% Done:|
|Target version:||2017-05-10 sprint|
|Story points||-||Remaining (hours)||0.00 hour|
|Velocity based estimate||-|
- 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".
#7 Updated by Radhika Chippada about 1 month ago
Branch 11250-container-state-display ready for review @ 8dd7e323798d36e3182c12868c6f1f3dd0eabf96