Available Tools
Tool Name | Description | ||
---|---|---|---|
Add Comment | Add a comment to a Jira issue.
IMPORTANT: The 'body' field must be provided in Atlassian Document Format (ADF), which is a JSON object, not a plain string. Example:
body: {
type: "doc",
version: 1,
content: [
{ type: "paragraph", content: [ { type: "text", text: "Your comment here." } ] }
]
}
You may also provide optional 'properties' (array of key/value objects) and 'visibility' (object specifying group/role restrictions).
See Atlassian Document Format documentation for details: https://developer.atlassian.com/cloud/jira/platform/apis/document/structure/ | Add Comment Add a comment to a Jira issue.
IMPORTANT: The 'body' field must be provided in Atlassian Document Format (ADF), which is a JSON object, not a plain string. Example:
body: {
type: "doc",
version: 1,
content: [
{ type: "paragraph", content: [ { type: "text", text: "Your comment here." } ] }
]
}
You may also provide optional 'properties' (array of key/value objects) and 'visibility' (object specifying group/role restrictions).
See Atlassian Document Format documentation for details: https://developer.atlassian.com/cloud/jira/platform/apis/document/structure/ | |
Add Worklog | Add a worklog to a Jira issue. | Add Worklog Add a worklog to a Jira issue. | |
Assign Issue | Assign a Jira issue to a user. | Assign Issue Assign a Jira issue to a user. | |
Create Issue | Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. A transition may be applied, to move the issue or subtask to a workflow step other than the default start step, and issue properties set.
The content of the issue or subtask is defined using update and fields. The fields that can be set in the issue or subtask are determined using the Get create issue metadata. These are the same fields that appear on the issue's create screen.
IMPORTANT: The 'description' field (and other textarea fields) MUST be provided in Atlassian Document Format (ADF), which is a JSON object, not a plain string. Example:
description: {
type: "doc",
version: 1,
content: [
{ type: "paragraph", content: [ { type: "text", text: "This is a description." } ] }
]
}
Creating a subtask differs from creating an issue as follows:
- issueType must be set to a subtask issue type (use Get create issue metadata to find subtask issue types).
- parent must contain the ID or key of the parent issue.
In a next-gen project any issue may be made a child providing that the parent and child are members of the same project
| Create Issue Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. A transition may be applied, to move the issue or subtask to a workflow step other than the default start step, and issue properties set.
The content of the issue or subtask is defined using update and fields. The fields that can be set in the issue or subtask are determined using the Get create issue metadata. These are the same fields that appear on the issue's create screen.
IMPORTANT: The 'description' field (and other textarea fields) MUST be provided in Atlassian Document Format (ADF), which is a JSON object, not a plain string. Example:
description: {
type: "doc",
version: 1,
content: [
{ type: "paragraph", content: [ { type: "text", text: "This is a description." } ] }
]
}
Creating a subtask differs from creating an issue as follows:
- issueType must be set to a subtask issue type (use Get create issue metadata to find subtask issue types).
- parent must contain the ID or key of the parent issue.
In a next-gen project any issue may be made a child providing that the parent and child are members of the same project
| |
Delete Comment | Delete a comment from a Jira issue. | Delete Comment Delete a comment from a Jira issue. | |
Delete Issue | Delete a Jira issue. | Delete Issue Delete a Jira issue. | |
Delete Worklog | Delete a worklog from a Jira issue. | Delete Worklog Delete a worklog from a Jira issue. | |
Find Users | Find users by query string (e.g., name, email). | Find Users Find users by query string (e.g., name, email). | |
Get Accessible Resources | Get all accessible Atlassian Cloud instances for the authenticated user. You need to call this tool before using any other Jira tools to obtain the cloudId. | Get Accessible Resources Get all accessible Atlassian Cloud instances for the authenticated user. You need to call this tool before using any other Jira tools to obtain the cloudId. | |
Get Attachment | Get metadata for a Jira attachment, including a download URL. | Get Attachment Get metadata for a Jira attachment, including a download URL. |
Showing 1 to 10 of 26 tools