people asking for 10 years now. happy birthday.

i am very interested in getting this feature for my colleagues and myself as well. Would be very helpful to have a visual link on the board.

Rui:  Most people using Jira have never even experienced what it is like to create and manage dependencies with simple flow links like in traditional waterfall project management, and once they see it, they realize it's a far superior way than hunting and pecking for issue IDs across the enterprise, or whipping off a line of JQL for the purposes to:

1. Establish dependencies (blocking)

2. Communicate dependencies to leaders

3. Manage dependencies which often requires the actions of leaders

I need this to properly manage dependencies.

Most important driving factor for scrum tool, any priority on this ???

:+1 for this feature.  Some type of feature to quickly highlight blocked/blocking issues would be really useful for team members that aren't intimately managing the board every day.

There are probably quite a number of users like me, who have no ability to add on plugins to their ALM suite.  I want a visual overlay to Jira - make dependencies and show dependencies between issues.  Just a good old network diagram; which would also help leaders to visualize their inaction has significant downstream impact.

Memorizing issue IDs, so that you can make blocking and is blocked by relationships - well, that's  really old-fashioned, when you consider that traditional project management family of products (MS Project being the dominator) modus has had visual linking of tasks on network diagrams, on Gantt charts, etc. for 20+ years.  And the visualization is just plain built in to the way you link things together.  

My guess is that the future state of project management in general will be a hybrid of agile and traditional project management, and it would behoove Atlassian to adopt the good things from traditional pm like a highly visual environment.

It would also behoove the company to stop depending on users being able to handle simple coding tasks in JQL for rather simple searching functions.  Atlassian could take a context-sensitive default approach to 'filtering'.  Most users are working in their project world, and never have a need to search the entire enterprise with each search activity.  Those that don't code are never going to take the time to learn JQL and will simply just not use the product suite.  Massive missed opportunity by Atlassian, forcing use of JQL for stupid simple in context searching.

I agree with Krys! Being able to visualize dependencies on issues in other projects would be a valuable addition to our Kanban boards. It would really help connect the dots when dependencies are scattered across teams, especially where release-planning is concerned.

This issue is not raised for JiraCloud but it should too. 

Being able to visualise which issues in an upcoming release have dependencies on issues in other projects (and which versions in there) would be really valuable.

Epics are not always appropriate, as an issue can only be in one Epic, and are not great for visualisation either.  

The descriptions of the duplicates JSW-11906 and JSW-13375 are much better (more verbose).