If a requester on the dependency blocked the dependency but the Depends on team decides to reject the dependency due to lack of communication, the dependency will continue to display as blocked instead of wiping out the blocked status and updating the status to rejected. In essence it appears that the dependency is holding two statuses due to Reject no longer being an option to the Depends on team and unable to changed the blocked status on the requesting team side for them. When the blocked is released from the requesting side the dependency then reflects the rejected status. I would think that Reject would trump block and would overwrite the blocked status. It's also possible to have the dependency blocked on both the requester side, and depends on side at the same time, and reject status. This also causes issues with reporting. The dependency does not always appear in the export due to the confusion in status. (side note dependencies that are in a propose state does not always appear in reporting either).