18

In Jira, (probably) in next-gen board, when specifying relationship between two issues, I have the following choices:

enter image description here

-- i.e. specifically "[A] depends on [B]" and "[A] is blocked by [B]".

What is the difference? Does "is blocked by" imply some stronger kind of dependency? Or are meanings of these items just project-dependent (i.e. no universal guideline)?

Sasha
  • 283
  • 1
  • 2
  • 6

4 Answers4

23

Jira links are broadly used, as far as I can see, for an information-only purpose.

All in all, it boils down to how your team uses it.

With that in mind, it'll strongly depend on what is considered a "dependency" and a "blocker" in your context.

Given the following scenario:

foo depends on bar

foo is blocked by baz

One way of reading it is as:

  • Foo cannot be started until bar is completed
  • Foo was started but baz happened (an external factor, probably) and it's blocking it's progress

Which could be derived into:

  • Depends are used for known or planned activities
  • Blocks are used for unexpected activities
Tiago Cardoso
  • 8,645
  • 6
  • 29
  • 72
  • 6
    Simplified examples: "Icing a cake" is dependant on "baking a cake" - you can't ice a cake you don't have. "Baking a cake" can be blocked by "roasting a chicken", because your oven is currently unavailable / in use. – Chronocidal May 23 '19 at 08:39
  • @Chronocidal I'd agree with using block for the mentioned scenario, but it is a bit different from what's written in this answer - it certainly doesn't have to be "unexpected". – NotThatGuy May 23 '19 at 12:24
  • 1
    I would say "cannot be started or finished". Making a cake is dependent on having every required ingredient, but you can certainly start without having an ingredient which you only need at the end (although whether you should start is another question entirely). – NotThatGuy May 23 '19 at 12:27
  • I would say my 2 cents, I would not see it quite like that . In my impression blocked by means a task can't be started due to that blocked by task totally since it's blocked. However depends on means a functional dependency where the order of execution of processes is basically started, or originates in a dependency. Eg dependency being a webservice endpoint, whereas the task dependent being a webservice caller, request, connector. – FantomX1 Oct 13 '21 at 08:34
4

I have always looked at them in the following manner: Depends On indicates a relation and order of a task to another, and Blocked By is a task progress status.

Ren
  • 231
  • 1
  • 6
  • 1
    I agree with this. "Blocked by" is a current status, dependencies are forever – JollyJoker May 23 '19 at 10:32
  • Not wrongly said, but what you mentioned I tend to think it is a consequence, not the causal factor. The ramifications of this are that a blocked by defines that a blocked by is a complete stopper for implementing the functionality, whereas depends denotes the sequence flow of the business process. – FantomX1 Oct 13 '21 at 08:37
3

Though being a blocker or a dependency are colloquially similar, Jira Roadmap timeline view can treat them differently. By default:

"blocks"/"is blocked by" is the link type required for the Roadmap view to show issues as linked in the Gantt-style timeline view. If you manually/visually link issues within the Roadmap timeline view by clicking the link handle from one issue to another, it creates a link of this "blocks" type.

"depends on"/"is a dependency of" links are not reflected in the Roadmap timeline chart, nor are they the link type created when manually as described above for "blocks" link types.

This distinction is configurable for Advanced Roadmaps by a Jira administrator. It may be configurable for links in regular roadmaps, though the documentation is a little less clear about that.

Scott H
  • 131
  • 4
  • 1
    Although the "blocks" relationship is the default, that's configurable, right? It means one could also use "depends" relationship. – Tiago Cardoso Jul 20 '23 at 12:32
  • 1
    @TiagoCardoso, thanks for sharing the Jira configuration details. Based on your link, it does look like "one" could configure it to use "depends". However, it looks like the "one" who could change that configuration must be a Jira administrator (not just an admin of the specific Jira Board). Looks like it would affect your entire organization. – Scott H Jul 20 '23 at 19:33
  • 1
    @TiagoCardoso, actually, the link you shared is for Advanced Roadmaps, and it does say that it is configurable (again, by a Jira admin). However, the page specific to regular project roadmaps does not mention configurability, saying "the timeline can only show issues with the Blocks issue link type" – Scott H Jul 20 '23 at 19:39
  • Good catch, folks. Thanks! – Tiago Cardoso Jul 21 '23 at 09:03
1

Dependencies and blockers are the same thing. The difference in tag typically means whether the event was planned for or not, whether it presents an unusual problem to be solved, whether it is escalated for different sets of eyes and/or hands, and possibly which bucket of dollars is being used to work it.

David Espina
  • 37,143
  • 4
  • 34
  • 91