# See every open Confluence action item on one board

> Pull every unfinished task out of your meeting notes and project pages into one screen, sorted oldest first, and tick them off without leaving the board.

- Workflow type: app
- Services: Confluence, Jira, Slack
- Categories: Operations, Engineering
- Published: 2026-08-17

## What it does

- Collects every open action item from the Confluence spaces you choose and lists them on one board, oldest first, so nothing stays buried in a page nobody reopens.
- Shows who each item is assigned to, the page and meeting it came from, its due date, and how many days it has been sitting open.
- Opens on your own items by default, with tabs for everyone's items grouped by person and a dedicated overdue view.
- Ticking an item off the board marks it complete on the Confluence page itself, so the page stays correct and the item drops off your list straight away.
- Turns anything too big to tick off into a Jira ticket, and nudges a teammate on Slack with a short list of their overdue items.

## What you'll need

- A Confluence account with access to the spaces you want to watch
- Action items written as tick boxes on your Confluence pages, which is what the standard meeting notes template already creates
- A Jira account, if you want the button that turns a big action item into a ticket
- A Slack workspace, if you want to nudge people about their overdue items

## Prompt

Build me an action item desk: an app that pulls every unfinished task buried in our Confluence pages into one screen. Right now our action items are scattered across meeting notes that nobody ever reopens, so they quietly rot. The whole app is a single board plus a space picker.

Space picker. Let me choose which Confluence spaces the board watches, typically our meeting notes space plus a few project spaces. Populate the picker with Get Spaces and persist my selection so the board comes back to the same set every time I open it.

Read path, and please follow this exactly. Our Confluence catalog has no list tasks or search tasks operation, so do not invent one. For each watched space, list pages with Get Pages in Space, and use Search Content (CQL) when you want to narrow the scan to recently updated pages or pages carrying a label like meeting-notes. Then fetch each page with Get Page by ID requesting the storage body, and parse the task list markup out of the returned body. In storage format the tasks live in ac:task-list elements, and each ac:task carries ac:task-id, ac:task-status which is complete or incomplete, and ac:task-body which holds the task text, the assignee as a ri:user mention with an account id, and the due date as a time element with a datetime attribute. Keep only the tasks whose status is incomplete.

Resolve each assignee account id to a real name with Get User by ID, and cache those lookups so we are not refetching the same handful of people on every scan. Fetching page bodies is the expensive part of this app, so cache aggressively and give me a refresh control rather than rescanning on every render.

The board itself. One row per open action item, showing the task text, the assignee, the page it came from as a link, which meeting it came from using the page title and date, the due date, and how many days it has been sitting open. Sort oldest first so the items that have rotted longest are at the top. For days open, persist the date we first saw each task id and count from there, falling back to the page's created date the first time we scan a page, since the task markup does not carry its own created timestamp.

Tabs. Default to a mine view for whoever opened the app, matching the viewer to their Confluence account so each person lands on their own list. Then a by person tab that groups items by assignee, and an overdue tab showing everything past its due date, oldest first. In the by person tab, give unassigned tasks their own bucket and pin it at the top, because those are exactly the ones that rot when nobody is looking.

Ticking an item. A tick box on each row calls Update Task to mark that task complete, so the Confluence page itself stays correct rather than drifting out of sync with the board. Unticking reverses it and marks the task incomplete again. Completing an item should immediately drop it off the list, so update the board optimistically instead of waiting for a full rescan, and put the row back with an error message if the update fails.

Escalating an item. For anything too big to just tick off, an escalate button creates a Jira ticket with Create Issue, prefilled with the task text as the summary and a description that links back to the source Confluence page. Let me pick the project and issue type once in settings and reuse them. After the ticket is created, show its key on the row so nobody escalates the same item twice.

Nudging someone. A nudge button next to a person direct messages them their overdue items in Slack. Resolve the assignee to a Slack user with List Users, matching on email address, then Open a Conversation to get the direct message channel and Send a Message with a short list of their overdue items and links to the pages those items live on. Keep the message brief and friendly, a handful of bullets rather than a wall of text, and tell me in the UI when a person could not be matched to a Slack account instead of failing silently.

Two rules to bake in throughout: unassigned tasks always get their own visible bucket rather than being filtered away, and completing an item on the board drops it off the list right away.

## How to customize

- Choose which spaces the board watches, such as your meeting notes space plus a few project spaces
- Pick which tab opens first if you would rather land on the overdue view than your own items
- Change the wording of the nudge message, and how far past its due date an item has to be before it counts as overdue
- Set which Jira project new tickets land in and what issue type they use

## FAQ

### Where do the action items come from?

From the tick boxes people add to Confluence pages while writing notes. The board reads the pages in the spaces you pick and gathers every tick box that has not been ticked yet, so you do not have to tag or file anything specially.

### Does ticking something off the board change the actual Confluence page?

Yes. When you tick an item, the tick box on the original page is marked complete too, so the page stays accurate for anyone who opens it later. Unticking reverses it the same way.

### What happens to action items that nobody was assigned to?

They get their own bucket on the board rather than being hidden. Unassigned items are the ones most likely to be forgotten, so the board keeps them visible until someone picks them up or ticks them off.

### Do I need Jira and Slack for this to be useful?

No. The board works on its own with just Confluence. Jira only powers the button that turns a large action item into a proper ticket, and Slack only powers the nudge that direct messages someone their overdue items.

### Can it watch more than one space at a time?

Yes. You choose the spaces, so you can point it at your meeting notes space and several project spaces at once and see everything on a single list.

### Will everyone see the same board?

The board opens on your own action items, so each person lands on their own list. The other tabs show the whole team's items grouped by person and everything that is overdue.

Use this prompt in General Input: https://www.generalinput.com/prompts/see-every-open-confluence-action-item-on-one-board