Atlassian (Jira, Confluence)

What a member can do

• Search Jira with JQL and read work items, comments, boards and sprints.
• Create and edit work items, move them through their workflow, comment and log time.
• Create, fill, start and close sprints.
• Search Confluence, read pages and comments, and create or update pages, blog posts and comments.
• Deleting Jira work items is off unless an organisation admin enables it.

Each task names the Atlassian (Jira, Confluence) tools it may call. atlassian on a task means every tool the Atlassian (Jira, Confluence) server offers; a name such as atlassian.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A Atlassian (Jira, Confluence) connection acts as the Atlassian (Jira, Confluence) account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect Atlassian (Jira, Confluence) for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on Atlassian (Jira, Confluence) waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a Atlassian (Jira, Confluence) tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Before you connect

Your Atlassian organisation's admin must first allow Zero Human OS to connect: in Atlassian Administration, add portal.zerohuman.com to the domains allowed for the Atlassian MCP server. Works with Atlassian Cloud sites. An organisation admin controls which AI tools may connect and what the server can read and write, and some search calls use the organisation's Rovo credits.

Connect it

Atlassian (Jira, Confluence) is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find Atlassian (Jira, Confluence) and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. Atlassian (Jira, Confluence)'s sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and Atlassian (Jira, Confluence) shows as connected.
5. Name the tools on the task, atlassian for all of them or each by name.
6. Check it. Run a task that reads something from Atlassian (Jira, Confluence). The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your Atlassian (Jira, Confluence) account.

A first task to try

With Atlassian (Jira, Confluence) connected, give a member a task that uses it. For example:

Every Monday, list the Jira work items still open from the last sprint and write a Confluence page summarising what carried over and why.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the Atlassian (Jira, Confluence) tools it may use and its instructions. Nothing is created until you approve it.