Jira
Use Jira to find work, inspect issue details, create well-scoped tickets, and update fields or workflow status.
Before you start
Section titled “Before you start”Open Customize → Plugins and select this plugin. Add installs an available package; Uninstall means it is already installed. An offered Update refreshes its package version. Your deployment and administrator policy determine availability.
When Add Account is offered, follow its connection instructions using an authorized account that owns or can access the intended resource. If several accounts are connected, check the selected account and Default before the task. Reconnect refreshes an expired connection; an administrator setup notice needs administrator configuration.
Enable the plugin for the selected agent or task. On an installed plugin’s Tools table, check Enabled and the Approval setting for the operations you intend to use. New tasks use these settings; a pending approval still needs a decision. See agent setup and action approvals.

Plugin details under Customize → Plugins. The button shows the current installation state.
Turn a launch gap into a ticket
Section titled “Turn a launch gap into a ticket”- Ask Redbelt to discover the intended project, its issue types, and assignable users. Use the returned identifiers rather than assuming a project supports a particular type.
- Search that project for an existing accessibility review ticket for your project.
- Draft Complete Accessibility Review with acceptance criteria, your target date, and the intended owner.
- Review the project, issue type, assignee, description, and labels before requesting creation.
- Read the created issue using its returned key and check each field.
Check the project I select for an existing accessibility review issue. If there is none, prepare a Task with keyboard navigation and contrast checks as acceptance criteria. Ask me for the assignee and target date, and show me the project and draft before creating it.
Update work accurately
Section titled “Update work accurately”Search accepts structured filters or raw JQL; a supplied JQL query takes precedence over the structured filters. Request specific fields for a compact result and follow pagination when assessing a backlog.
Discover an issue’s available transitions before changing its status. In Review means completed work awaiting review when that is your team’s workflow; it should not automatically be treated as work still being implemented. Updates can change fields, add comments, resolve assignees, adjust labels, and create issue links. Inspect the returned verification for fields Jira rejected or ignored.
A Subtask needs its parent key in the creation request. Custom fields can require a discovered option or user identifier. The current catalog’s delete operation is disabled; this guide does not offer issue deletion.
Tool Reference
Section titled “Tool Reference”Thread and workflow availability are listed separately. A tool must also be enabled for your task and allowed by its account and administrator policy. Configure workflow app actions using only actions offered by the current picker.
Available Tools
Section titled “Available Tools”| Tool | Required Fields | Thread | Workflow |
|---|---|---|---|
atlassian_jira.create_issue |
projectKey, issueTypeName, summary |
Yes | Yes |
atlassian_jira.discover |
resource |
Yes | Yes |
atlassian_jira.get_issue |
issueIdOrKey |
Yes | Yes |
atlassian_jira.search_issues |
No mandatory top-level fields | Yes | Yes |
atlassian_jira.update_issue |
issueIdOrKey |
Yes | Yes |
Required fields above are the schema minimum. The target, selected operation, or account can impose additional requirements.
atlassian_jira.create_issue — Create a Jira issue.
Optional fields: additionalFields, assigneeAccountId, assigneeSearchString, comments, customFieldUpdates, description, labels, linkOperations, parentKey.
atlassian_jira.discover — One discovery tool for Jira metadata.
Optional fields: fieldNameOrId, issueIdOrKey, issueTypeId, maxResults, projectIdOrKey, searchString.
atlassian_jira.get_issue — Get a single Jira issue by key (e.g.
Optional fields: fields.
atlassian_jira.search_issues — Search Jira issues.
Optional fields: assignee, createdAfter, createdBefore, fields, filters, issueType, jql, labels, maxResults, nextPageToken, orderBy, projectKey, status, text, updatedAfter, updatedBefore.
atlassian_jira.update_issue — Update a Jira issue in one call.
Optional fields: addLabels, additionalFields, assigneeAccountId, assigneeSearchString, comments, customFieldUpdates, description, linkOperations, parentKey, priorityName, removeLabels, setLabels, summary, transitionComment, transitionFields, transitionId, transitionName, unassign.
Troubleshoot
Section titled “Troubleshoot”If a transition or custom field fails, discover the project-specific metadata and reread the issue. An OAuth connection does not guarantee access to every project or permission to assign every user.
Provider details: Jira documentation.