Shipfox

Jira agent tools

Look up the Jira tools, selectors, permissions, inputs, and outputs available to agent steps.

This reference lists the shipped Jira agent-tool catalog. See the Jira overview for authentication and setup.

Selectors

Use a standalone tool selector in an agent step's integrations: block. For the agent integration contract, see the workflow schema reference.

Tool catalog

Jira read tools require the read:jira-work OAuth scope. Jira write tools require write:jira-work, and the workflow step's integrations entry must set allow_write: true or Shipfox rejects the step at validation.

tools

get_issue

Retrieve a Jira issue by its ID or key.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: get_issue

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
fieldsarrayOptional
fieldsByKeysbooleanOptionalInterpret fields by their keys instead of IDs
expandstringOptionalComma-separated Jira issue expansions
propertiesarrayOptional
updateHistorybooleanOptionalRecord this issue as viewed by the authorizing user

search_issues

Search Jira issues with a JQL query.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: search_issues

Input
FieldTypeRequiredDescription
jqlstringRequiredJira Query Language expression
maxResultsintegerOptionalMaximum number of issues to return
nextPageTokenstringOptionalPagination token from a previous search
fieldsarrayOptional
fieldsByKeysbooleanOptionalInterpret fields by their keys instead of IDs
expandstringOptionalComma-separated Jira issue expansions
propertiesarrayOptional
reconcileIssuesarrayOptional

get_issue_comments

List the comments on a Jira issue.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: get_issue_comments

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
startAtintegerOptionalZero-based comment offset
maxResultsintegerOptionalMaximum number of comments to return
orderBystringOptionalComment ordering expression
expandstringOptionalComma-separated Jira comment expansions

get_issue_transitions

List the workflow transitions available for a Jira issue.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: get_issue_transitions

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
expandstringOptionalComma-separated transition expansions, such as transitions.fields

get_project

Retrieve a Jira project by its ID or key.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: get_project

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira project ID or key, such as ENG
expandstringOptionalComma-separated Jira project expansions
propertiesarrayOptional

get_user

Retrieve a Jira user by Atlassian account ID.

Sensitivity: read.

Sensitive: No.

Required permissions: read

Selector tokens: get_user

Input
FieldTypeRequiredDescription
accountIdstringRequiredAtlassian account ID
expandstringOptionalComma-separated Jira user expansions

create_issue

Create a Jira issue using Jira REST issue fields. If both a project key and project ID or both an issue type name and issue type ID are supplied, the ID takes precedence.

Sensitivity: write.

Sensitive: No.

Required permissions: write

Selector tokens: create_issue

Input
FieldTypeRequiredDescription
projectKeystringOptionalJira project key; projectId takes precedence if both are supplied
projectIdstringOptionalJira project ID; takes precedence over projectKey
summarystringRequiredIssue summary
issueTypestringOptionalIssue type name; issueTypeId takes precedence if both are supplied
issueTypeIdstringOptionalIssue type ID; takes precedence over issueType
assigneeAccountIdstringOptionalAtlassian account ID to assign
prioritystringOptionalJira priority name
labelsarrayOptional
bodystringOptionalPlain-text issue description
fieldsobjectOptionalJira issue fields keyed by their REST API field name
updateobjectOptionalJira issue field update operations

update_issue

Update a Jira issue using Jira REST issue fields.

Sensitivity: write.

Sensitive: No.

Required permissions: write

Selector tokens: update_issue

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
summarystringOptionalReplacement issue summary
issueTypestringOptionalReplacement issue type name; issueTypeId takes precedence if both are supplied
issueTypeIdstringOptionalReplacement issue type ID; takes precedence over issueType
assigneeAccountIdstringOptionalAtlassian account ID to assign
prioritystringOptionalReplacement Jira priority name
labelsarrayOptional
bodystringOptionalPlain-text replacement issue description
fieldsobjectOptionalJira issue fields keyed by their REST API field name
updateobjectOptionalJira issue field update operations

add_comment

Add a plain-text comment to a Jira issue.

Sensitivity: write.

Sensitive: No.

Required permissions: write

Selector tokens: add_comment

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
bodystringRequiredPlain-text comment body

transition_issue

Move a Jira issue through a workflow transition.

Sensitivity: write.

Sensitive: No.

Required permissions: write

Selector tokens: transition_issue

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
transitionIdstringRequiredJira workflow transition ID
fieldsobjectOptionalJira issue fields keyed by their REST API field name
updateobjectOptionalJira issue field update operations

assign_issue

Assign or unassign a Jira issue by Atlassian account ID.

Sensitivity: write.

Sensitive: No.

Required permissions: write

Selector tokens: assign_issue

Input
FieldTypeRequiredDescription
idOrKeystringRequiredJira issue ID or key, such as ENG-123
accountIdstring | nullRequiredAtlassian account ID, or null to unassign
Was this page helpful?
Edit this page on GitHub

On this page