See what is blocking a Jira issue and what is waiting on it, upstream and downstream, colour-coded by status, in one glance. No setup, and it works on any workflow.
Open a Jira issue and you can see its links, but not the shape of them. Throughline reads the issue's links and lays them out around it. Everything it depends on, its blockers, fans out to the left, upstream. Everything waiting on it fans out to the right, downstream. Anything already done collapses into a tray below. Each linked issue shows its key, summary, real relationship and status colour, so you can see what is holding the issue up and what you will unblock when it lands, without opening every link.
The issue you are viewing sits in the centre. Linked issues are placed by the direction of the relationship and coloured by Jira's universal status category, so it works on any workflow regardless of your custom status names.
Every row shows its real relationship wording, "is blocked by", "blocks", "is caused by", taken straight from the link type, so nothing is renamed or guessed. Click any linked issue to open it, or use Copy keys to copy every linked key as a ready-made search.
Every Jira link type defines an inward and an outward phrase, and Throughline uses that to place each link. An issue you "are blocked by", or "are caused by", or "are gated by", sits upstream. An issue you "block", or "cause", or "gate", sits downstream. Because this comes from the wording every type already carries, it works on any link type, including ones you have renamed or created yourself. The red blocking marker is applied to recognised blocking relationships. An unfamiliar custom type is still placed correctly by direction, just shown without the marker.
Throughline shows one issue's direct dependencies. It deliberately does not roll up dependencies across an epic's children or your wider portfolio. It answers "what does this issue depend on, and what depends on it?", not "what is the aggregated risk beneath this epic?". Because Jira links are point-to-point, a child blocked under another epic will not change the parent epic's view here. It is also not a planner or a scheduler, and it never scores or judges your work. It shows the dependencies and trusts you to read them.
Throughline runs entirely on Atlassian's infrastructure, under the Runs on Atlassian programme. It is strictly read-only and makes no external network calls, so your data never leaves Atlassian. It reads only the issue you are currently viewing, its links, subtasks and parent, along with the status and summary of the directly-linked issues. It stores nothing and collects no personal data, and it honours your existing Jira permissions, so it only ever shows what the viewing user can already see. Full details are in our privacy policy.
Questions, issues or feedback? Email contact@productiversed.com and we will get back to you.
Throughline is one of a small set of apps for Jira and Confluence that turn the data your team already creates into something you can use.
See all our apps