Is there any real advantage or compelling reason to link issues?

[Jim Stewart]

If I link activities in a Gantt chart to show dependencies, the reason is clear. I can see how they relate to each other and if the predecessor slips, so does the successor.

In Jira I can say B is blocked by A. but so what? Other than saying that - which doesn't even seem to manifest on the task board - why would I do that? They don't really seem to move together nor would it be obvious to a stakeholder looking at the board that they are in any way connected. 

[John Funk · Accepted solution]

Hi Jim,

You are correct - just because you link them, nothing happens automatically. You might explore adding some automation that when the Start Date or End Date (or Due Date) for one changes then it changes the one linked to it. 

[Jim Stewart]

Hmm. Ok. I'm pretty familiar with automation. It may be overkill for us - or for anyone - given that sprints are so short. However, I have some thinking to do on the roadmap side of things where, if I understand correctly, the epics are linked. Thanks. 

[Dave Rosenlund _Trundl_]

Hi, @Jim Stewart. You may also wish to explore apps that let you create WBS boards where you can organize Jira issues according to their dependecies (i.e., hierarchically) — even if they are not in the same projects. 

This search will help you get started:

      https://marketplace.atlassian.com/addons/app/jira/top-selling?hosting=cloud&query=hierarchy

"The big three" in this category are:

• (Advanced) Roadmaps from Atlassian
• BigPicture from Software Plant
• Structure for Jira from ALM Works (note, I work for ALM Works)

Hope this helps, 

-dave