“Is there a recommended workflow for [task/project] we should follow?”

[Balogun Olumide]

Hi team, I want to better track progress on our tasks using Confluence and Jira. Could someone explain the recommended way to link Jira tasks with Confluence pages, monitor deadlines, and generate progress reports? Any existing dashboards or templates the team uses would be very helpful.”

[David Freitez]

Hi @Balogun Olumide ,

Here’s how we usually do this in a clean, “works long-term” way with Jira and Confluence in my opinion:

1. Linking Jira tasks to Confluence pages (recommended setup)
   1. Use a Jira issue key everywhere it makes sense. If a Confluence page is about a delivery, decision, or mini-project, add the related Jira epic/story key(s) on the page.
   2. In Confluence, use the Jira macro (the “Jira issues” / “Jira” embed).** That lets you show a live list of issues based on:
      1. a saved filter, or
      2.  a JQL query (example below), or
      3. a link to a board/backlog.
   3. In Jira, link back to the Confluence page using the Confluence “Link” panel (or “Confluence pages” integration depending on how your Jira is configured). That way anyone in Jira can jump straight to the doc/spec/status page.
   4. If you want it to be tidy: make the Confluence page the “single place” for context/status, and Jira the “single place” for task execution.
   5. Example JQL you can embed in Confluence:
      1. All issues in an epic: `parentEpic = EPIC-123` (or whatever field name your instance uses)
      2. Due soon / overdue: `duedate <= endOfWeek() AND statusCategory != Done`
      3. Just the important ones: `project = ABC AND labels = initiative-x ORDER BY duedate ASC`
2. Monitoring deadlines:
   1. Jira Dashboard approach (most common):
      1. Add gadgets like Filter Results, Pie Chart, Two-Dimensional Filter Statistics (Status x Assignee), Created vs Resolved, etc.
      2. Create and reuse a couple of saved filters like:
         1. “Overdue” (due date in the past, not Done)
         2. “Due next 7 days”
         3. “Blocked / needs attention”
      3. Board approach (good for daily flow):
         1.  Use the board + Quick Filters (e.g., “Due this week”, “My issues”, “High priority”).
         2. If you’re Kanban, set WIP limits and watch cycle time; if Scrum, watch sprint commitments and spillover.
      4. Calendar/timeline options (if enabled in your instance):
         1. Some teams use Calendar-style views (or Plans/Timeline) to spot deadline collisions. It depends on what apps/features we have turned on.
   2. Generating progress reports:
      1.  Quick status summary on a Confluence page (best for stakeholders)
         1. Put a short status section at the top: RAG status (Green/Amber/Red), key risks, next milestones.
         2. Under that, embed Jira issue tables that auto-update:
            1. “In Progress”
            2. “Done this week”
            3. “Overdue / at risk”
            4. “Blockers”
      2. Jira Dashboard as the source of truth (best for real-time reporting)
         1. Make a dashboard per initiative/team and pin:
            1. Progress by status (pie)
            2. Work by assignee/status (2D stats)
            3. Overdue list (filter results)
            4. Created vs resolved 
      3. You can check for Confluence Templates here: https://www.atlassian.com/software/confluence/templates

Hopefully this helps you answer your inquiry, if so, please vote for it as the answer to your question.

Kind regards,
David