If a linked issue is "blocked by" the current issue why would it need to be done/deployed to close the current issue.
We are trying to create dependencies by using blocks and blocked by.
It doesn't make sense to require the blocked issue to be deployed/done to close the epic that was blocking it.
Hi @Angi Hast,
I tend to 100% agree with that statement. However, it is very likely that this is a restriction that was implemented by someone administering your site. Automatically blocking an issue from reaching a status based on conditions from linked issues (or based on any conditions at all) is not something I have seen Atlassian include by default anywhere in Jira.
I would suggest checking in with your Jira admins to verify any conditions applied to your Jira workflows in the project(s) where you see this behaviour.
Hope this helps!
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.