Show issue is blocked even when user doesn't have visibility to the blocking issue
Problem to solve
This is a follow on to issue #34723 (closed) which is the issue to Visually Differentiate Blocked Issues.
From a discussion on issue 34723, a decision was made to not show the blocking issue visual indicator if a user did not have access to the blocking issue. The rationale was that if a user cannot influence the blocking issue, then it doesn't help them to know that it's blocked.
A valid point was raised that there may still be some benefit to show that issues are blocked to more accurately reflect status and level-set expectations for progress.
Intended users
Further details
This issue is to explore whether or not it is beneficial to show users that issues are blocked when they don't have the permissions to view the blocking issue.
The user story we are solving for is:
As a product manager on another team, I would like to know that an issue is blocked (even if I cannot see what is blocking it) so I can better understand the timeframe for issue resolution.
As a development lead using issue boards, knowing that an issue is blocked (even if I cannot view why) provides important input to scheduling work.
As a software developer, it is beneficial for me to see blocked issues (even if I cannot view why) as I know that they may not be resolved immediately, which may help me better prioritize work.
Proposal
Expand the functionality of #34723 (closed) to allow users who do not have visibility into the blocking issue to still see the blocked issue notification icon.
Permissions and Security
TBD