Steps:
1) make 2 jobs share a lock: A and B
2) kick off job A
3) try to kick off job B.
4) Job B will be queued up as "pending". A mouse-over shows that the lock is blocking. This is correct.
5) edit job A and remove the lock.
6) Job B will still be queued up as "pending". Now when mousing over job B in the queue no reason for pending is listed.
7) I remove job B from the queue and try to run it again, but it is still in the same #6 state

I'm assuming that job B would run when A finished, but I could not wait.

So that I could run job B I ended up temporarily removing the lock from Job B.

This removing lock situation is not common so I'm marking the priority as minor for now.