start using Jira with your agents
sign up, open a project, and authorise Jira from its connectors settings.
a jira issue describes the work, and the moment it is created, moved or commented on is usually when someone wants an agent to pick it up. connecting jira to an aldena project turns those moments into runs: an agent creates an event routine on an issue or a whole jira project from a chat, and the next matching event starts a run in that chat, or in a new chat in the same project when the routine opens one per event. because each conversation in the aldena project gets its own sandbox, that agent can then do the engineering work behind the ticket. reading and changing issues goes through atlassian's mcp server.
subscribing from a chat
jira_subscribe takes a resource, the events to watch, and what the agent should do when one arrives. the resource is an issue key such as ALD-42, or a jira project key such as ALD for every issue in that jira project. an issue routine fires when the issue is updated or commented on, and a jira project routine also fires when a new issue is created. jira_unsubscribe takes an event routine off again, and the aldena project's Settings → Routines lists every routine the agents hold.
each notification carries the event routine, the actor, a one-line summary and a link. a new issue also carries its description as plain text, and a comment carries the comment as plain text. the text is fenced off as untrusted data and capped at 4,000 characters, so a ticket can inform the agent but cannot instruct it.
connecting a site
the connection authorises against one jira cloud site. when the account can reach more than one, the connectors row asks which site this aldena project should use before it finishes. aldena registers the webhook that delivers issue and comment events every time the aldena project connects, so a reconnect also repairs a webhook that went missing.
going beyond triggers with atlassian's mcp server
for reading issues with jql, creating and editing them, commenting and transitioning, add atlassian's mcp server to the same project. it acts as the person who signs in to it.
- an atlassian org admin adds aldena's domain to the rovo mcp server's allowlist in atlassian administration, so the sign-in can return to aldena.
- open the project's Settings → Connectors, and under MCP servers press Marketplace.
- install Atlassian, open the sign-in link it gives you, and approve access in the browser.
once it is connected, agents reach its tools through mcp_search and mcp_call, each tool gets its own row in the project's permissions, and every action runs as the person who signed in, not as aldena. the mcp servers page covers the rest.
example tasks
- 01
when anything new lands in the mobile project, draft a plan for it here.
the routine on the jira project starts a run in this chat for each new issue, with the description in the notification. the agent reads the repository in the conversation's sandbox and proposes an approach.
jira_subscribegithub_git_syncbash - 02
take ALD-142, build it, and move it to in review when the branch is up.
it does the work in the conversation's sandbox, pushes a branch, then transitions the issue and links the branch through atlassian's mcp server.
github_git_syncbashgithub_git_pushmcp_searchmcp_call - 03
whenever someone comments on ALD-200, answer if it is a question about the api.
each comment starts a run with the comment's text. the agent checks the code and replies on the issue through atlassian's mcp server, or here in the chat when the project has none.
jira_subscribemcp_call
what it will not do
the connector does not search, create, edit, comment on, transition or delete issues, and board, workflow and permission schemes are out of reach. an agent cannot subscribe to a jira project the connected account cannot see, and no event starts a run while the connection waits for a reconnect.
what starts a run
every Jira event an agent can subscribe to, grouped by resource. an agent subscribes from a chat with jira_subscribe, and each matching event starts a run in that chat, or in a new chat in the same project when the routine opens one per event.
issue.createdissue.updatedissue.commented
what you grant
aldena asks Jira for exactly this access on the consent screen, the same set for every project. there is nothing to pick, and nothing else is requested.
- Read issues and projects
read:jira-workCheck the projects and issues agents subscribe to.
- Manage webhooks
manage:jira-webhookRegister the webhook that delivers issue and comment events from the site.
- Stay connected
offline_accessRefresh the connection without asking you to sign in again.
how to connect Jira
connecting Jira takes one authorisation round trip, started from inside the project that needs it.
- open the project's connectors settings
connections belong to a project, not to your account or the team. open the project that needs Jira, go to settings → connectors, and press connect. other projects stay untouched.
- authorise with a real account
any member of the project can start the connection, and they authorise as themselves. Jira asks only for the fixed access listed above, with no scopes to choose.
- an agent subscribes from a chat
ask an agent in a project chat to watch something in Jira. it calls jira_subscribe with the resource, events and intent, and settings → routines lists each routine it holds.
- a matching event starts a run
each matching event starts a run with the event and its content in hand, in the chat where the agent subscribed or in a new chat in the same project when the routine opens one per event. disconnecting Jira stops every subscription to it.
data handling and security
a connector holds one credential and turns Jira events into runs. the credential stays inside the project that connected it, and event text is data, never instructions.
- one connection, one project
the Jira credential is stored against the project it was authorised in. no agent in another project can use it, and there is no team-wide connection to inherit by accident.
- tokens encrypted at rest
the Jira token is encrypted before it is stored, and it never appears in a chat or in an agent's prompt. agents get the events, not the credential.
- events only where a routine watches
aldena verifies each delivery came from Jira. an event starts a run only for a routine it matches, in the chat that set the routine up or in a new chat in the same project when the routine opens one per event. nothing starts while the connection needs a reconnect.
- event content is untrusted
event text may come from a stranger. it reaches the agent as fenced data capped at 4,000 characters, and the agent is told never to follow instructions in it.
- revocation is one click
disconnect Jira and the project's event routines on it stop at once, along with the stored credential.

each Jira tool agents hold has its own allow, ask or deny row in the project's permissions. see human in the loop for approvals and isolated projects for isolation.
faq
can ai agents be used in jira?
yes, in two parts. the jira connector starts runs: an agent creates an event routine on an issue or a jira project with jira_subscribe, and each created, updated or commented issue starts a run in that chat, or in a new chat in the same project when the routine opens one per event. reading, creating, commenting on and transitioning issues goes through atlassian's mcp server, added from the aldena project's mcp marketplace.
is there an ai tool for jira that also does the engineering work?
that is the point of connecting jira to an aldena project rather than installing a ticket assistant. each conversation in the aldena project gets its own sandbox, so the agent that a jira event woke up can clone the repository, write the change, run the tests and push a branch, then move the issue through atlassian's mcp server.
which jira permissions does aldena ask for?
read:jira-work to check the jira projects and issues agents subscribe to, manage:jira-webhook to register the webhook that delivers issue and comment events, and offline_access to keep the connection alive without signing in again. there is nothing to pick, and nothing that writes to jira.
what does a jira event notification contain?
the event routine, the actor, a one-line summary and a link. a new issue also carries its description as plain text, and a comment carries the comment as plain text. that text is fenced off as untrusted data and capped at 4,000 characters, and an update arrives with the summary alone.
how do i connect atlassian's mcp server for jira?
an atlassian org admin first adds aldena's domain to the rovo mcp server's allowlist. then open the aldena project's settings, connectors, mcp servers, press marketplace, install atlassian and finish the browser sign-in. its actions run as the person who signed in, not as aldena.
spin up your first project.
one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.
