beehiivA customer asks when the export bug will be fixed. You realize you haven’t opened Jira since Monday. The ticket is still in To Do, right where you left it.
Jira had the answer the whole time. You just weren’t in Jira.
What the board shows from Jira and Confluence
One Atlassian sign-in covers both. From Jira, the board can show your open issues as a live list, your Jira board’s active sprint, or the result of any Jira search. One project, one assignee, bugs only, newest first. If you know JQL, use it. If you don’t, tell your agent what you want and it writes the search.
From Confluence it can show a page, or what is in a space. Put the launch checklist that lives in Confluence on the board, right beside the issues that block it.
Every form shows what the widget will say before it is added. And because it’s your board, Jira sits next to Sentry’s unresolved errors, your revenue and today’s commits, not in a tab of its own.
Where the data comes from
Atlassian runs a remote MCP server for Jira and Confluence. The board signs in to it with Atlassian’s own sign-in, and Atlassian applies your existing permissions. The board sees what your account can see and nothing else.
That server can also create issues and edit pages for agents that ask. The board never runs those tools. It only runs the ones that read, so a ticket never moves because of the board.
The board reads while it is open, on the schedule you pick. A read that fails keeps the last good list and says what went wrong and when.
Why put Jira on a board
Jira holds every ticket. On a busy day you need the five that matter, and you need them next to everything else.
A board puts those five beside your revenue, your errors and the agents working on them. Start from a blank canvas, or ask your agent to add Jira to the board you already have.