Connect Atlassian to Warp
Give Warp governed access to Atlassian’s 96 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Atlassian to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Atlassian in Runlayer
Add Atlassian from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Atlassian’s 96 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Atlassian
Sign in the way Atlassian requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Atlassian from Warp
Atlassian’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
96 Atlassian tools in Warp
Runlayer policy decides which of these Warp users can call. 12 read data only and 1 can change or delete data.
Add comment to Jira issue
Add or update a comment on a Jira issue
Add Confluence content permissions
Adds one or more content-level permission grants to a single Confluence content entity.
Add Confluence reaction
Add emoji reaction to Confluence content
Add connections to goals
Add one type of connection to one or more Atlassian Goals.
Add connections to projects
Add one type of connection to one or more Atlassian Projects.
Add Teamwork Graph context
Adds a relationship between two entities in the Teamwork Graph (e.g. linking two Jira work items, marking one as blocking another, attaching a remote link, or connecting a Jira work item to an Atlas…
Add labels to Confluence content
Add labels to any Confluence content (page, blogpost, attachment, custom content)
Add or edit Jira issue comment
Add a comment to a Jira issue, or edit an existing one: omit commentId to add, or pass one from listJiraIssueComments to edit.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Atlassian call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more