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
- Navigate to CrewAI AMP Integrations
- Find Jira in the Authentication Integrations section
- Click Connect and complete the OAuth flow
- Grant the necessary permissions for issue and project management
- 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..env file:
Available Actions
jira/create_issue
jira/create_issue
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
- Options:
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.
jira/update_issue
jira/update_issue
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
- Options:
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.
jira/get_issue_by_key
jira/get_issue_by_key
Description: Get an issue by key in Jira.Parameters:
issueKey(string, required): Issue Key (example: “TEST-1234”).
jira/filter_issues
jira/filter_issues
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,$stringLessThanlimit(string, optional): Limit results - Limit the maximum number of issues to return. Defaults to 10 if left blank.
jira/search_by_jql
jira/search_by_jql
Description: Search issues by JQL in Jira.Parameters:
jqlQuery(string, required): JQL Query (example: “project = PROJECT”).paginationParameters(object, optional): Pagination parameters for paginated results.
jira/update_issue_any
jira/update_issue_any
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.
jira/describe_action_schema
jira/describe_action_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.
jira/get_projects
jira/get_projects
Description: Get Projects in Jira.Parameters:
paginationParameters(object, optional): Pagination Parameters.
jira/get_issue_types_by_project
jira/get_issue_types_by_project
Description: Get Issue Types by project in Jira.Parameters:
project(string, required): Project key.
jira/get_issue_types
jira/get_issue_types
Description: Get all Issue Types in Jira.Parameters: None required.
jira/get_issue_status_by_project
jira/get_issue_status_by_project
Description: Get issue statuses for a given project.Parameters:
project(string, required): Project key.
jira/get_all_assignees_by_project
jira/get_all_assignees_by_project
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
- 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
- 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
- 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
- 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
- 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.
