Skip to main content

Overview

Enable your agents to manage issues, projects, and workflows through Jira. Create and update issues, track project progress, manage assignments, and streamline your project management with AI-powered automation.

Prerequisites

Before using the Jira integration, ensure you have:
  • A CrewAI AMP account with an active subscription
  • A Jira account with appropriate project permissions
  • Connected your Jira account through the Integrations page

Setting Up Jira Integration

1. Connect Your Jira Account

  1. Navigate to CrewAI AMP Integrations
  2. Find Jira in the Authentication Integrations section
  3. Click Connect and complete the OAuth flow
  4. Grant the necessary permissions for issue and project management
  5. Copy your Enterprise Token from Integration Settings

2. Install Required Package

3. Environment Variable Setup

To use integrations with Agent(apps=[]), you must set the CREWAI_PLATFORM_INTEGRATION_TOKEN environment variable with your Enterprise Token.
Or add it to your .env file:

Available Actions

Description: Create an issue in Jira.Parameters:
  • summary (string, required): Summary - A brief one-line summary of the issue. (example: “The printer stopped working”).
  • project (string, optional): Project - The project which the issue belongs to. Defaults to the user’s first project if not provided. Use Connect Portal Workflow Settings to allow users to select a Project.
  • issueType (string, optional): Issue type - Defaults to Task if not provided.
  • jiraIssueStatus (string, optional): Status - Defaults to the project’s first status if not provided.
  • assignee (string, optional): Assignee - Defaults to the authenticated user if not provided.
  • descriptionType (string, optional): Description Type - Select the Description Type.
    • Options: description, descriptionJSON
  • description (string, optional): Description - A detailed description of the issue. This field appears only when ‘descriptionType’ = ‘description’.
  • additionalFields (string, optional): Additional Fields - Specify any other fields that should be included in JSON format. Use Connect Portal Workflow Settings to allow users to select which Issue Fields to update.
Description: Update an issue in Jira.Parameters:
  • issueKey (string, required): Issue Key (example: “TEST-1234”).
  • summary (string, optional): Summary - A brief one-line summary of the issue. (example: “The printer stopped working”).
  • issueType (string, optional): Issue type - Use Connect Portal Workflow Settings to allow users to select an Issue Type.
  • jiraIssueStatus (string, optional): Status - Use Connect Portal Workflow Settings to allow users to select a Status.
  • assignee (string, optional): Assignee - Use Connect Portal Workflow Settings to allow users to select an Assignee.
  • descriptionType (string, optional): Description Type - Select the Description Type.
    • Options: description, descriptionJSON
  • description (string, optional): Description - A detailed description of the issue. This field appears only when ‘descriptionType’ = ‘description’.
  • additionalFields (string, optional): Additional Fields - Specify any other fields that should be included in JSON format.
Description: Get an issue by key in Jira.Parameters:
  • issueKey (string, required): Issue Key (example: “TEST-1234”).
Description: Search issues in Jira using filters.Parameters:
  • jqlQuery (object, optional): A filter in disjunctive normal form - OR of AND groups of single conditions.
    Available operators: $stringExactlyMatches, $stringDoesNotExactlyMatch, $stringIsIn, $stringIsNotIn, $stringContains, $stringDoesNotContain, $stringGreaterThan, $stringLessThan
  • limit (string, optional): Limit results - Limit the maximum number of issues to return. Defaults to 10 if left blank.
Description: Search issues by JQL in Jira.Parameters:
  • jqlQuery (string, required): JQL Query (example: “project = PROJECT”).
  • paginationParameters (object, optional): Pagination parameters for paginated results.
Description: Update any issue in Jira. Use DESCRIBE_ACTION_SCHEMA to get properties schema for this function.Parameters: No specific parameters - use JIRA_DESCRIBE_ACTION_SCHEMA first to get the expected schema.
Description: Get the expected schema for an issue type. Use this function first if no other function matches the issue type you want to operate on.Parameters:
  • issueTypeId (string, required): Issue Type ID.
  • projectKey (string, required): Project key.
  • operation (string, required): Operation Type value, for example CREATE_ISSUE or UPDATE_ISSUE.
Description: Get Projects in Jira.Parameters:
  • paginationParameters (object, optional): Pagination Parameters.
Description: Get Issue Types by project in Jira.Parameters:
  • project (string, required): Project key.
Description: Get all Issue Types in Jira.Parameters: None required.
Description: Get issue statuses for a given project.Parameters:
  • project (string, required): Project key.
Description: Get assignees for a given project.Parameters:
  • project (string, required): Project key.

Usage Examples

Basic Jira Agent Setup

Filtering Specific Jira Tools

Project Analysis and Reporting

Automated Issue Management

Advanced Schema-Based Operations

Troubleshooting

Common Issues

Permission Errors
  • Ensure your Jira account has necessary permissions for the target projects
  • Verify that the OAuth connection includes required scopes for Jira API
  • Check if you have create/edit permissions for issues in the specified projects
Invalid Project or Issue Keys
  • Double-check project keys and issue keys for correct format (e.g., “PROJ-123”)
  • Ensure projects exist and are accessible to your account
  • Verify that issue keys reference existing issues
Issue Type and Status Issues
  • Use JIRA_GET_ISSUE_TYPES_BY_PROJECT to get valid issue types for a project
  • Use JIRA_GET_ISSUE_STATUS_BY_PROJECT to get valid statuses
  • Ensure issue types and statuses are available in the target project
JQL Query Problems
  • Test JQL queries in Jira’s issue search before using in API calls
  • Ensure field names in JQL are spelled correctly and exist in your Jira instance
  • Use proper JQL syntax for complex queries
Custom Fields and Schema Issues
  • Use JIRA_DESCRIBE_ACTION_SCHEMA to get the correct schema for complex issue types
  • Ensure custom field IDs are correct (e.g., “customfield_10001”)
  • Verify that custom fields are available in the target project and issue type
Filter Formula Issues
  • Ensure filter formulas follow the correct JSON structure for disjunctive normal form
  • Use valid field names that exist in your Jira configuration
  • Test simple filters before building complex multi-condition queries

Getting Help

Need Help?

Contact our support team for assistance with Jira integration setup or troubleshooting.