-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
It is frustrating for the users, when they see that the "Waiting for" job has finished, but they are still locked (because another job got the resource first), only now they can't see why, or who is the blocker.
Suggestion is that the log for jobs waiting for the same resource should be updated every time the resource is passed to another job. (would be nice to be able to see the whole queue if possible)