Real problems from Jira, Confluence and monday.com teams, worked through with sources. Each article starts from a question teams actually asked and ends with what the platform can do natively, what it cannot, and where one of our apps fits.
A JQL due-date filter in the Jira work items macro lists overdue work for one team at a time; the Jira chart macro's listed fields do not include Team. What works natively, the exact JQL, and a live overdue count per team. Checked 9 Nov 2026.
Jira has swimlanes per assignee, epic or space, but none per team. Query swimlanes fill the gap: one JQL lane per Atlassian team. The menu path, the clauses, who can do it and the limits. Checked 8 Nov 2026.
monday.com cross-project dependencies link tasks across project boards on the Enterprise plan: the Dependent On column, FS/SS/FF/SF types, red conflicts in the Gantt view and a widget. Limits and the alternative for other plans. Checked 7 Nov 2026.
The Jira Cloud REST API v3 creates an issue link with POST /rest/api/3/issueLink, returns nothing but a 201, and needs Browse projects plus Link issues. The request body, how to get the new link's ID, the permissions, the error codes and the scopes, from Atlassian's API reference. Checked 6 Nov 2026
Three ways to put the dependencies between teams on the Confluence page you use for PI or quarterly planning: Jira work items macros with link JQL, an embedded Jira plan (Premium and Enterprise), or a dependency graph macro. What each one shows and where it stops. Checked 5 Nov 2026.
JQL can find the work items linked to one item, but it cannot compare the Team field at both ends of a link. What the native Jira work items macro can show, a per-item blocker list, and a live who-waits-on-whom table by team. Checked 4 Nov 2026.
A board quick filter is a JQL clause, and the Team field's JQL compares team ids, not names. How to find the id, the clause to paste, who can add it, and a name-based version. Checked 3 Nov 2026.
The monday.com API reads dependencies through DependencyValue, filters items with any_of, not_any_of, is_empty and is_not_empty, and writes them with change_multiple_column_values. Queries, gotchas and limits, checked 2 Nov 2026.
The Jira timeline only draws Blocks links, only between work items in the same space, and only when an admin has work item linking switched on. What each rule means, how to add and remove a dependency on the timeline, and what to do with the links it cannot show. Checked 1 Nov 2026.
JQL can find work items that have an "is blocked by" link, but not where the blocker lives. What the Jira work items macro can show on a Confluence page, the workItemLink and linkedWorkItems() workarounds, and when a graph helps. Checked 31 Oct 2026.
Native Confluence macros chart Jira work by assignee or status, not by Atlassian team. What the Jira chart and Jira work items macros can show, the JQL for one team's open and overdue work, and a live per-team workload table. Checked 30 Oct 2026.
The Atlassian Team field takes a team id, not a name. How to find the field's customfield id and the team id, the Edit issue body that sets it, why sub-tasks cannot have their own team, and the JQL to check the result. Checked 29 Oct 2026.
The monday.com Dependency column links items on the same board only. For work that waits on another board, use a Connect boards column. What each column stores, what the API returns, and how to see the result. Checked 28 Oct 2026.
A Jira admin adds a custom link type under Settings > Work items > Work item linking with a name, an outward and an inward description. The steps, what deleting a type does, the REST API permissions, and how to keep the list short. Checked 26 Oct 2026.
A Jira work items macro with project = ABC AND sprint in openSprints() AND workItemLinkType = "is blocked by" keeps a stand-up or sprint review page current. What it shows, what it misses (the blockers, chains, other teams) and when a graph helps. Checked 24 Oct 2026.
Jira's velocity chart lives on one scrum board and the Confluence Jira chart macro has no velocity chart. What you can put on a page with native tools, where the numbers differ, and a per-team velocity table across boards. Checked 23 Oct 2026.
The Atlassian Team field is not on every Jira layout by default. Where to add it in company-managed and team-managed spaces, the permission it needs, the 15-team limit for linked teams, and why workflows need the Team UUID. Checked 22 Oct 2026.
monday.com dependencies only shift dates that already exist. Blank Date or Timeline cells, the wrong mode, batch edits and plan limits are the usual reasons nothing moves. The fixes, from monday's own docs. Checked 21 Oct 2026.
A Jira Automation rule with a Work item transitioned trigger and a Linked work items branch on the "blocks" link can comment on, or move, every work item the finished one was blocking. The steps, the limits, and what the rule cannot see. Checked 20 Oct 2026.
Put a Jira work items macro on the release page with fixVersion plus workItemLinkType = "is blocked by". What that list shows, what it cannot show (the blockers themselves, their status, chains), and when a graph macro helps. Checked 19 Oct 2026.
IS EMPTY queries in the Jira work items macro give a live list of open work with no owner, no estimate or no due date. The exact JQL, a count tile per gap, what the native macros miss. Checked 18 Oct 2026.
Team-managed Kanban boards lost the manual \"Clear now\" action in Atlassian's board update. What is left: hide done items after 1, 7, 14, 30 or 60 days in View settings, the Release route on company-managed boards, and a JQL list for the week's finished work. Checked 17 Oct 2026.
Yes: the Gantt view and widget can highlight the critical path in red, on Pro and Enterprise, and monday still calls it a trial feature. How to turn it on, what it needs and what it does not show. Checked 16 Oct 2026.
LinkLens for Jira is approved and public on the Atlassian Marketplace. It draws every blocker chain in a Jira project on one canvas, flags circular dependencies in red and adds the chain to each issue. Free up to 10 users.
Put a Jira work items macro on the page with the JQL linkedWorkItems(KEY) or workItemLink, optionally by link type. What the native list shows, where it stops, and when a graph macro helps.
Jira's linkedWorkItems() JQL function (long known as linkedIssues()) finds everything linked to one work item, optionally by link type. What it can do, the link fields next to it, and the limits.
Two JQL queries (updated < \"-2w\" and status CHANGED) in the Jira work items macro give a live stale-work list in Confluence. What they miss, and a per-team option. Checked 12 Oct 2026.
Jira has no recurring-issue feature (JRACLOUD-5185, 194 votes, closed Won't Fix). A scheduled Automation rule creates them: setup, cron, the step allowance per plan. Checked 11 Oct 2026.
List an epic's children with parent = KEY, spot the blocked ones, then list their blockers with issueBlocks in (...). Tested JQL, limits and a graph macro.
Jira's timeline reads only the Blocks link type, Plans treats every link as Blocks by default, and JQL can't isolate "blocks". What that means for your link type.
Jira Issues macro, Jira Chart macro, an embedded dashboard or gadget, or an embedded board: what each shows in Confluence, its limits, and when to use it.
monday.com has one pre-built recipe that changes a dependency's status, and the custom builder can't use the Dependency column at all. What the recipe offers, what it can't do, and how to see which tasks are ready.
Jira Automation can set the Team field when the assignee changes: one branch per team, now with a native team picker. What it cannot do, and how to find work it missed.
Atlassian now lets admins merge teams. What merging, archiving and deleting a team do to the Team field on Jira work, to JQL, and to the team hierarchy.
Jira's new descendantsOfTeam() JQL function finds work for a team and its sub-teams. What Atlassian announced, what worked in our test, and what it lacks.
Jira Cloud's Workload Pie Chart, Issue Statistics and board reports never group by the Atlassian Team field. Here is what a per-team workload view needs, how far native Jira gets, and how TeamLens reports it across projects.
The Dependency column and the Gantt view show one link at a time. How to see whole chains, catch loops and get a dependency health report on any monday.com board.
Confluence's Jira Issues and Jira Chart macros cannot group work by the Atlassian Team field. What they can do, the workarounds, and a live team report macro.
Confluence can list Jira issues and embed timelines, but not draw blocker chains from issue links. The native options, why hand-drawn diagrams go stale, and a live graph macro.
Jira records every "is blocked by" link but shows them one issue at a time. Here is how to turn issue links plus the Team field into a cross-team dependency report, what native Jira offers, and how TeamLens builds the matrix.
Jira's Pie Chart, Issue Statistics and Two Dimensional gadgets cannot group by the Atlassian Team field. Here is why, the usual workaround, and a cleaner fix.
Jira lets A block B, B block C and C block A without a warning. How the loops form, why Atlassian's own detection needs database access, and a faster way.