This issue is happening to me at https://pagure.io/fegistry/issue/2. Also, this issue combines with https://pagure.io/pagure/issue/1678 in a bad way because now there's no way I can close issue 2 in my project. I also noted in my ticket that the logic is reversed (the issue that is blocked is the one that doesn't make sense to close, but the blocking ticket should be closable).

I did find a workaround for not being able to close my issue number 2. Though you can't edit number 2 to drop the blocking relationship, you can edit the other ticket and remove the depends relationship there. After you do that, you can go back to the other ticket and the relationship is removed.

Fixing the backwards logic would really help though.

There's still a caveat to my workaround - you can only edit the relationship from the other side if that ticket doesn't also have dependency relationships. In my case, https://pagure.io/fegistry/issue/2 blocks https://pagure.io/fegistry/issue/3, which currently depends on other issues that aren't yet fixed. The only thing I can do to close https://pagure.io/fegistry/issue/2 is to drop the blocking relationships all the way down.

This is seriously affecting us. We have a ticket that depends on another ticket which in turns blocks it. Since both tickets have the blocked-by/depends-on metadata, we are unable to touch either of them.

Before this bug is fixed, can we somehow work around it?

Another related problem is that semantic of blocks/depends is different as it should be. https://pagure.io/pagure/issue/1966

Commit 484b1f3 relates to this ticket

Commit 3ab3365 fixes this issue