Jira Dependency Map and Cross-Team Risk Briefing
Make dependencies visible before they cause delay.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Create a dependency map for Jira issues across teams. Epics and key stories with owners and dates: [WORK_ITEMS]. Dependencies as I understand them (A needs B): [DEPENDENCIES]. Teams and their sprint rhythm: [TEAMS]. Make a table with the dependent item, the item it waits on, owning team, link type (blocks or is blocked by) [VERIFY link types in my project], needed-by date, expected date, slack in days, and rank. Worked slack: Story A needed by 14 May and expected 16 May is minus 2 days; Story B needed 21 May and expected 19 May is plus 2. Rank negative slack first, then uncertainty and number of items waiting. Use my dates, and flag any date that is missing instead of assuming it. Mitigation menu with the question for each: can we split, mock the interface, pair with the other team, or change the sequence. Draft a half-page briefing with Decisions needed, Risks, Next two weeks and Asks to other teams, plus a plain-text timeline. Coordination meeting script: 3 minutes on the top risks, 2 minutes per risk to agree an owner and date, with decisions recorded in Jira comments. Escalation rule for a dependency more than a week late, a template message asking another team for a firm date without blaming them, and a weekly update routine with a named owner of the map.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.