Skip to content

docs: clarify user requirements for built-in Jira tools #820

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
warp-agent-staging wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify user requirements for built-in Jira tools #820

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/content/docs/factories/integrations/jira.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,10 @@ When the run finishes, the result appears in the agent session. The agent doesn'
* **A connected Jira user becomes the run's creator, not its agent** - [Connect your Jira account to Warp](/platform/integrations/jira/#connecting-your-jira-account-to-warp) so a session you start is attributed to you; an unconnected account gets a prompt to connect instead of a run starting. Either way, the run executes as the agent selected by the automation, not as that Jira user.
* **Jira access doesn't include code access** - Connecting Jira lets agents read and update Jira work items, nothing more. Repository access comes from the factory itself.

:::caution
Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](https://docs.warp.dev/platform/mcp) instead; it uses the access of the account it was connected with.

@warp-for-oss warp-for-oss Bot Oct 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Use a root-relative internal docs link here to match the docs style guide and the surrounding page's links.

Suggested change
Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](https://docs.warp.dev/platform/mcp) instead; it uses the access of the account it was connected with.
Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](/platform/mcp/) instead; it uses the access of the account it was connected with.

:::

## Troubleshooting

* **Warp is unavailable in Jira** - Confirm the Warp app is installed on the Jira Cloud site. On the app's **Configure** page, click **Connect to Warp** if the installation isn't connected to a workspace.
Expand Down
Loading