Skip to main content

​
Jira Integration

Jira integration enables Annie to access your issue tracker, allowing it to search tickets, retrieve issue details, and correlate incidents with existing bugs, tasks, and historical issues.

​
Setup Guide

  1. Go to the Anyshift integrations page
  2. Navigate to the Knowledge Base section
  3. Select Jira
  4. Click Connect Jira
  5. Enter your Jira Domain, Email, and API Token
  6. Click Save

​
1. Jira Domain

Enter your Atlassian domain (e.g., yourcompany.atlassian.net). This is the URL you use to access Jira Cloud. For example, if you access Jira at https://acme.atlassian.net, enter acme.atlassian.net.

​
2. Email

Enter the email address associated with your Atlassian account (e.g., user@company.com).

​
3. API Token (Scoped Token Required)

Anyshift uses Atlassian’s official Remote MCP server, which requires a scoped API token. Classic API tokens are not supported.

​
Step 1: Enable API Token Authentication (Admin Required)

An organization admin must first enable API token authentication for the Rovo MCP server:
  1. Go to Atlassian Admin
  2. Navigate to Settings > Rovo > Manage external tool access
  3. Enable API token authentication for the MCP server
  4. Save your changes
For more details, see Atlassian’s Remote MCP Server documentation. Without this admin configuration, API token authentication will fail with a 401 error.

​
Step 2: Create a Scoped API Token

Generate a scoped API Token with Jira read permissions:
  1. Go to Atlassian API Token Management
  2. Click Create API token
  3. Select Scoped token type (not Classic)
  4. Enter a label (e.g., “Anyshift Integration”)
  5. Grant the following scopes:
    • read:jira-work - Read Jira issues and projects
    • read:jira-user - Read user information
  6. Click Create
  7. Copy the token and paste it into Anyshift
For more details, see Atlassian’s API Token documentation. Important: Classic API tokens do not work with Atlassian’s Remote MCP server. You must create a scoped token with the required Jira permissions. Keep your API token secure and do not share it publicly.

​
Required Permissions

Annie performs read-only operations on your Jira instance. Your API Token grants access based on your Atlassian account permissions. Your account needs access to:
  • View projects
  • View issues and their details
  • Search issues using JQL
Annie does not create, modify, or delete any issues, comments, or other content in your Jira instance.

​
How It Works

Once connected, Annie can leverage your Jira instance during:
  • Incident Investigation: When analyzing an incident, Annie searches for related issues, bugs, and historical tickets to find relevant context and past resolutions
  • Question Answering: When you ask about specific tickets or projects, Annie retrieves the details directly from Jira
  • Correlation: Annie can correlate alerts and incidents with existing Jira tickets to identify known issues

​
Example Use Cases

  • “Search Jira for authentication issues from the last week”
  • “Get details on ticket INFRA-1234”
  • “Find all high-priority bugs in the Platform project”
  • “What Jira tickets are related to Redis connection issues?”
Annie will search your Jira instance using JQL (Jira Query Language) and cite relevant issues in its responses.

​
JQL Query Examples

Annie can construct JQL queries automatically based on your questions:
QuestionJQL Query
”Recent bugs”type = Bug AND created >= -7d ORDER BY created DESC
”Open high priority issues”priority = High AND status != Done
”Authentication issues”text ~ "authentication" OR summary ~ "auth"
”Issues in Platform project”project = PLATFORM ORDER BY updated DESC

​
Supported Features

Annie can access the following Jira data: Issues
  • Search issues using JQL
  • Get full issue details (summary, description, status, priority, assignee, etc.)
  • View available status transitions
Projects
  • List all accessible projects
  • Get project details and metadata
Metadata
  • Get available issue types for a project
  • Get custom field definitions

​
Security

  • API tokens are encrypted at rest using AWS KMS
  • Anyshift only reads from your Jira instance (no write operations)
  • All communication uses HTTPS/TLS encryption
  • Credentials are transmitted securely via Atlassian’s official Remote MCP server

​
Troubleshooting

​
”401 Unauthorized” or “Invalid credentials” error

This is usually caused by one of the following:
  1. API token authentication not enabled: An organization admin must enable API token authentication for Rovo MCP. See Step 1 above.
  2. Using a classic token instead of scoped token: Classic API tokens do not work with Atlassian’s Remote MCP server. Create a scoped token with Jira read permissions. See Step 2 above.
  3. Token missing required scopes: Ensure your scoped token has the read:jira-work and read:jira-user scopes.
  4. Email/token mismatch: Verify your email matches your Atlassian account email exactly.

​
”No issues found” when searching

  • Verify your account has permission to view the projects being searched
  • Check that the JQL query syntax is valid
  • Ensure issues exist matching your search criteria

​
Connection timeout

  • Verify your Jira domain is correct (e.g., yourcompany.atlassian.net)
  • Check that your Atlassian instance is accessible

​
”You don’t have permission to connect via API token”

This error indicates that API token authentication has not been enabled by your organization admin. Contact your Atlassian admin to:
  1. Go to Atlassian Admin > Settings > Rovo > Manage external tool access
  2. Enable API token authentication
  3. Save changes
See Atlassian’s Remote MCP documentation for more details. Ready to get started? Configure Jira Integration