​
Overview

​
Tool Name

jira_connector_tools

​
Purpose

The jira_connector_tools group integrates Genesis workflows with Jira. Authenticate to a Jira instance, create or update issues, search with JQL, transition statuses, and pull project metadata to keep work in sync.

​
Key Features & Functions

Authenticate & Connect

Establish a secure session with your Jira Cloud or Server instance.

Create & Update Issues

Open new tasks, bugs, or stories and modify fields, assignees, and priorities.

Search with JQL

Run targeted queries to find and report on issues across projects.

Workflow Transitions

Move issues through statuses using valid transition IDs.

Project Context

Fetch projects, issue types, and workflow options to drive automation.

​
Input Parameters for Each Function

​
jira_connector

Parameters
NameDefinitionFormat
actionOperation to perform. Supported: authenticate, create_issue, update_issue, get_issue, search_issues, get_projects, create_project, get_workflows, transition_issue.String (required)
jira_urlBase URL of the Jira instance. Example: https://yourcompany.atlassian.net.String
usernameJira username or email for authentication.String
api_tokenAPI token or password for authentication.String
project_keyProject key for issue actions.String
issue_keySpecific issue key for get, update, or transition.String
issue_typeType for new issues. Common: Bug, Task, Story, Epic, Subtask.String
summaryTitle for the issue.String
descriptionDetailed description body.String
assigneeUsername or account id to assign.String
priorityPriority value. Common: Highest, High, Medium, Low, Lowest.String
labelsLabels to apply.Array of strings
custom_fieldsMap of custom field ids to values.Object
transition_idWorkflow transition id when moving status.String
jql_queryJQL for search operations.String
max_resultsMaximum number of results to return.Integer
Prefer API tokens over passwords for Jira Cloud. Create tokens from your Atlassian account and store them securely.

​
Use Cases

  1. Auto-create incidents from platform events When a data quality check fails, open a Bug in the correct project with context attached.
  2. Sync task progress Move issues to In Progress or Done when Genesis tasks are started or completed.
  3. Programmatic reporting Run scheduled JQL searches for open blockers and post summaries to Slack.
  4. Sprint coordination Batch update assignees and priorities ahead of sprint planning.
  5. Governance and audits Pull full issue details with history and attachments for compliance reviews.
**Deleting or bulk editing issues in Jira is hard to undo. **Test your automation in a non-production project first.

​
Workflow/How It Works

  1. Authenticate Provide jira_url, username, and api_token to establish a session.
  2. Operate on issues Use create_issue, update_issue, get_issue, and transition_issue as tasks progress.
  3. Search and report Execute search_issues with jql_query to produce lists for dashboards or alerts.
  4. Pull context Call get_projects and get_workflows to discover valid types, fields, and transitions.
Custom fields vary by project. Use get_issue on a known ticket or the Jira REST API browser to confirm field ids before automating writes.

​
Integration Relevance

  • project_manager_tools to mirror milestones and task states.
  • data_dev_tools to tie engineering work to Jira user stories.
  • slack_tools to notify channels on issue creation or failure transitions.
  • file_manager_tools to attach logs, screenshots, or reports to issues.
  • delegate_work to hand off Jira updates as part of multi-agent workflows.

​
Configuration Details

  • Use the full HTTPS base URL for your instance.
  • Ensure the API token has permissions for the target projects.
  • Match project_key, issue_type, and custom field ids to the project configuration.
  • Workflow transitions require valid transition_id for the issue’s current status.

​
Limitations or Notes

  1. Jira Cloud and Server have capability differences that can affect endpoints.
  2. API rate limits may require pagination or backoff for large queries.
  3. Permissions and screens can block writes to required fields if not supplied.
  4. Large searches should use pagination through max_results and offsets.
  5. Tokens expire or can be revoked. Handle authentication failures gracefully.

​
Output

  • Authentication Confirmation of the authenticated user and scopes.
  • Issue Operations Keys, URLs, updated field snapshots, and current status after actions.
  • Search Results Arrays of issues with key metadata from JQL queries.
  • Project and Workflow Data Project listings, issue types, transitions, and related configuration.
  • Errors Clear messages for permission problems, invalid fields, missing transitions, or connectivity issues.