EvergreenDocs

Use Jira and Confluence with Evergreen

Connect Atlassian so the agent can search, read, and update Jira issues and Confluence pages as you.

The Atlassian integration lets the agent work in Jira and Confluence as you. It uses Atlassian’s own MCP server, so the agent has the same permissions your Atlassian account has, and changes carry your name.

What the agent can do

  • Search Jira with JQL and read whole issues, with their comments and transitions.
  • File, edit, comment on, and transition Jira issues when you ask.
  • Search Confluence and read or write pages in your spaces.
  • Link its commits and pull requests to the issue it’s working on.
  • Use Atlassian’s own skills for triage, status reports, and turning a spec into a backlog.

When your task names an issue key such as PROJ-123, the agent reads the issue before it plans. When the work ends in commits, it’s told to put the key in the commit messages and the pull request title so Jira links them, and to comment on the issue with the pull request once it opens.

The same Atlassian server offers some other Atlassian tools too, such as Bitbucket Cloud and Loom. Each one stays behind your own permissions, and an Owner or Admin can block any tool.

Who can connect it

An Owner or Admin installs it for the workspace. Then each person connects their own Atlassian account. The integration signs in on its own, so there’s no app to create and nothing to copy. If your Owners and Admins have turned on Members can connect integrations that need no setup, a member can connect it without waiting for an install. See How integrations work for that setting.

Connect Atlassian

  1. Open Integrations

    An Owner or Admin opens Workspace settings › Integrations, finds Atlassian, and chooses Install.

  2. Sign in

    Choose Sign in as yourself. Atlassian opens, you approve the request, and you come back to Evergreen. This becomes your own connection.

  3. Choose who can use it

    Pick Everyone, Selected audiences, or Only me, then finish the install.

  4. Connect each person

    Each person goes to Settings › Integrations, finds Atlassian, and chooses Connect.

What it asks before changing things

While the agent plans, it reads Jira and Confluence. Filing, editing, commenting on, and transitioning issues, and writing pages, become available once you approve the plan, or from the start if you skip the plan. The agent is told to create, edit, or transition things only when the task asks. See Plans and asks for how approval works.

An Owner or Admin can block individual tools for everyone on the Tools tab in Manage. Blocked tools aren’t offered to the agent in anyone’s session.

Start sessions from Jira

An automation can start a session when someone creates, updates, or comments on a Jira issue. See Start sessions automatically.

Limits

  • Atlassian’s own administrators control the server. In Atlassian Administration › Rovo › Rovo MCP server, they decide whether it’s on for your organization.
  • Two groups of admin-only tools, delete_jira and manage_jira, are off by default. Until an Atlassian admin turns them on, the agent can’t delete issues or create projects.
  • Jira Service Management tools need API tokens, so they aren’t available here.
  • The agent sees what your Atlassian account can see, and nothing else.

Troubleshooting

What you see What to do
After you approve the request, Atlassian shows a page saying access to the domain is restricted An Atlassian organization admin has to allow Evergreen’s address, the one the page names, under Atlassian Administration › Rovo › Rovo MCP server › Domain settings. Add it with /** at the end. If the page keeps appearing, remove the entry and add it again, then try in a fresh private window.
The sign-in was canceled or took too long Try again and finish the sign-in in the same tab.
The agent can’t delete an issue or create a project An Atlassian admin has to turn on the delete_jira or manage_jira tool group.
The agent can’t reach Jira or Confluence at all An Atlassian admin may have turned the Rovo MCP server off for your organization. Ask them to check Atlassian Administration › Rovo › Rovo MCP server.
The Atlassian card shows Reconnect Your authorization lapsed. Choose Reconnect to sign in again.
There’s no Install button Only Owners and Admins install integrations. Ask one of them, or choose Request.

Last updated

Esc