Catch up on Confluence and Jira with sweeps
A sweep checks your Confluence spaces or Jira projects on a schedule and tells you what changed and what needs you. It spends while nobody watches, within limits you set.
A sweep keeps an eye on one place your team works, a Confluence wiki or a Jira board, and reports back on a schedule: what changed, what you might do about it, and anything it could not read. Each run is called a pass.
Open it from the sidebar under Productivity > Sweeps. The tabs are My work, Confluence and Jira.
Set up a sweep#
Open the Confluence or Jira tab and choose Setup.
Under Connect Confluence (or Connect Jira), enter the Site address, your Atlassian email and an Atlassian API token.
Click Test connection (free), then Save credential.
Under What to sweep, tick the spaces or projects to watch.
Pick How often, then turn on the schedule switch. It then reads Running on a schedule.
Advanced shows the work window (the hours and days it may run), Most passes per day, Most minutes per pass and Warn me above (USD per day). The warning only tells you; it never stops a pass. Run now runs one pass straight away, which spends and counts toward today's limit.
Typing or saving a credential works only in the desktop app, never from your phone.
Stop every sweep at once#
Turn on Stop all sweeps at the top of the panel. It takes effect within about a minute, before any new pass starts, and stays on after a restart. To stop one sweep, turn off its schedule switch, or pause it.
Read what a pass found#
The Dashboard of each source shows the latest findings grouped by kind, each with a link, a checklist of things you might want to do, and a health list of anything it skipped or could not read. A pass that finds nothing says so.
A place that fails is tried once more, then set aside and shown in the health list instead of being retried forever.
Work through your Jira tickets#
The Jira tab lists your tickets from the projects you picked, grouped by Next step, such as Blocked, Stale, Ready to start and In review / Shipping. Each row can:
Assign to me, Move to... and Comment: change the ticket in Jira, on your click only, with no AI.
Research: start a read-only agent session about the ticket.
Build it: start an agent session on a new branch; when it finishes, Yardmaster opens a draft pull request.
Snooze: hide it for a while. Snoozing never deletes anything.
Research and Build it each start a normal agent session on your Claude plan, one per click.
My work gathers the tickets waiting on you into Now, Today, Soon and Later, without any AI and at no cost.
Sharpen. On some tickets, Sharpen drafts acceptance criteria with one small AI call billed to your Anthropic API key, not your Claude plan: about two cents at most per click, and never more than about $1 a day. You edit the lines, then Add to Jira adds them to the end of the description.
Summaries. Passes can also write a short summary of each ticket that changed. They ride on the pass you already pay for; they make each pass a little longer.
Agents and sweeps. An agent can ask for workbench actions, but anything that starts a session or changes Jira waits for your approval in the Inbox.
The old Jira board. The built-in Jira board, with its columns, backlog and sprint planning, was removed. The Jira tab here is how Yardmaster works with Jira now.
Not a sweep of its own. House Rules uses the same money rules and the same Stop all sweeps switch: see House Rules.