Link Issues - What has to be done first?

[Deleted user]

Hello everybody,

I have a question for the community how JIRA is designed in the terms of dependency.

Here is an example 

What is the correct understanding of above mentioned ticket:

1️⃣ - Ticket PANX-3938 has to be done before QEUI-230 and MEM-1679

OR

2️⃣ - Tickets QEUI-230 and MEM-1679 have to be done before PANX-3938

Thanks for the answer :-

[Els Bassant]

Hi @[deleted] , and welcome to the community!

The image you added doesn't load for me, but going off the most common link types:

• Blocks - the current issue is blocking another issue. This means the current issue needs to be done first.
• Is blocked by - the current issue is blocked by another issue. This means the other issue needs to be done first.

If the issue links that you posted are different, can you try posting the image again?

[Deleted user]

Hello Els, I re-uploaded the image. You can check it now. Thanks

[Mark Segall]

Hi @[deleted] and welcome to the community.  You'd want to set up something like this:

1. On PANX-3938 you would set up two issue links to QEUI-230 and MEM-1679.  Each would be set up as "Blocks"
   1. Once this is done, QEUI-230 and MEM-1679 would each show "Is Blocked By" PANX-3938
2. On PANX-3938 you would set up two issue links to QEUI-230 and MEM-1679. Each would be set up as "Is Blocked By"
   1. Once this is done, QEUI-230 and MEM-1679 would each show "Blocks" PANX-3938

[Deleted user]

Hello Mark, thank you for your answer :)

I re-uploaded the image in case you have not seen it before. My questions is about when our JIRA has dependencies called "has to be done before/has to be done after".

I found out that this is confusing for my colleagues and maybe we will switch to "blocks/is blocked by" :)

[Mark Segall]

Thanks for re-uploading the image.  It would seem that for your use case that your first option would be the interpretation

...and yes - I find it very rare that I need to deviate from the stock link types provided by Atlassian. The Blocks issue type is tried and true and less typing when you need to execute a query (e.g. issueIsBlockedBy = PANX-3938)