Skip to main content
PinkConnect service: jira | Type: Application (parent with child servers) | PCID required: Yes Jira Cloud is exposed as multiple MCP server IDs (one per area below). Each child server has its own server path and tool names.

Child servers

Child serverServer pathToolsDescription
jira-issues/jira-issues41Jira Issues - search, create, update, transition issues; manage comments, attachments, links, watchers, votes, worklogs, and saved filters
jira-projects/jira-projects18Jira Projects - browse projects, components, versions, statuses, categories, and dashboards
jira-users/jira-users8Jira Users - find and look up users, groups, and permissions

jira-issues

Jira Issues - search, create, update, transition issues; manage comments, attachments, links, watchers, votes, worklogs, and saved filters Server path: /jira-issues | Type: Application | PCID required: Yes

Tools

ToolDescription
jira_issues_add_commentAdd comment
jira_issues_add_voteAdd vote
jira_issues_add_watcherAdd watcher
jira_issues_add_worklogAdd worklog
jira_issues_assign_issueAssign issue
jira_issues_bulk_fetch_issuesBulk fetch issues
jira_issues_count_issuesCount issues using JQL
jira_issues_create_filterCreate filter
jira_issues_create_issueCreate issue
jira_issues_delete_commentDelete comment
jira_issues_delete_filterDelete filter
jira_issues_delete_issueDelete issue
jira_issues_delete_worklogDelete worklog
jira_issues_do_transitionTransition issue
jira_issues_edit_issueEdit issue
jira_issues_get_all_labelsGet all labels
jira_issues_get_attachmentGet attachment metadata
jira_issues_get_attachment_metaGet Jira attachment settings
jira_issues_get_auto_complete_postGet field reference data (POST)
jira_issues_get_commentGet comment
jira_issues_get_commentsGet comments
jira_issues_get_create_issue_meta_issue_type_idGet create field metadata for a project and issue type id
jira_issues_get_create_issue_meta_issue_typesGet create metadata issue types for a project
jira_issues_get_edit_issue_metaGet edit issue metadata
jira_issues_get_favourite_filtersGet favorite filters
jira_issues_get_filterGet filter
jira_issues_get_filters_paginatedSearch for filters
jira_issues_get_issueGet issue
jira_issues_get_issue_linkGet issue link
jira_issues_get_issue_link_typesGet issue link types
jira_issues_get_issue_watchersGet issue watchers
jira_issues_get_my_filtersGet my filters
jira_issues_get_transitionsGet transitions
jira_issues_get_votesGet votes
jira_issues_get_worklogGet worklog
jira_issues_link_issuesCreate issue link
jira_issues_remove_voteDelete vote
jira_issues_remove_watcherDelete watcher
jira_issues_search_and_reconsile_issues_using_jql_postSearch for issues using JQL enhanced search (POST)
jira_issues_update_commentUpdate comment
jira_issues_update_filterUpdate filter

jira_issues_add_comment

Add comment Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
expandstringNoUse expand to include additional information about comments in the response. This parameter accepts renderedBody, which returns the comment body rendered in HTML.
authorobjectNoThe ID of the user who created the comment.
bodyobjectNoThe comment text in Atlassian Document Format.
createdstringNoThe date and time at which the comment was created.
idstringNoThe ID of the comment.
jsdAuthorCanSeeRequestbooleanNoWhether the comment was added from an email sent by a person who is not part of the issue. See Allow external emails to be added as comments on issuesfor information on setting up this feature.
jsdPublicbooleanNoWhether the comment is visible in Jira Service Desk. Defaults to true when comments are created in the Jira Cloud Platform. This includes when the site doesn’t use Jira Service Desk or the project isn’t a Jira Service Desk project and, therefore, there is no Jira Service Desk for the issue to be visible on. To create a comment with its visibility in Jira Service Desk set to false, use the Jira Service Desk REST API Create request comment operation.
propertiesany[]NoA list of comment properties. Optional on create and update.
renderedBodystringNoThe rendered version of the comment.
selfstringNoThe URL of the comment.
updateAuthorobjectNoThe ID of the user who updated the comment last.
updatedstringNoThe date and time at which the comment was updated last.
visibilityobjectNoThe group or role to which this comment is visible. Optional on create and update.

jira_issues_add_vote

Add vote Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.

jira_issues_add_watcher

Add watcher Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
bodystringYesThe account ID of the user. Note that username cannot be used due to privacy changes.

jira_issues_add_worklog

Add worklog Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key the issue.
notifyUsersbooleanNoWhether users watching the issue are notified by email.
adjustEstimatestringNoDefines how to update the issue’s time estimate, the options are: * new Sets the estimate to a specific value, defined in newEstimate. * leave Leaves the estimate unchanged. * manual Reduces the estimate by amount specified in reduceBy. * auto Reduces the estimate by the value of timeSpent in the worklog.
newEstimatestringNoThe value to set as the issue’s remaining time estimate, as days (#d), hours (#h), or minutes (#m or #). For example, 2d. Required when adjustEstimate is new.
reduceBystringNoThe amount to reduce the issue’s remaining estimate by, as days (#d), hours (#h), or minutes (#m). For example, 2d. Required when adjustEstimate is manual.
expandstringNoUse expand to include additional information about work logs in the response. This parameter accepts properties, which returns worklog properties.
overrideEditableFlagbooleanNoWhether the worklog entry should be added to the issue even if the issue is not editable, because jira.issue.editable set to false or missing. For example, the issue is closed. Connect and Forge app users with Administer Jira global permission can use this flag.
authorobjectNoDetails of the user who created the worklog.
commentobjectNoA comment about the worklog in Atlassian Document Format. Optional when creating or updating a worklog.
createdstringNoThe datetime on which the worklog was created.
idstringNoThe ID of the worklog record.
issueIdstringNoThe ID of the issue this worklog is for.
propertiesany[]NoDetails of properties for the worklog. Optional when creating or updating a worklog.
selfstringNoThe URL of the worklog item.
startedstringNoThe datetime on which the worklog effort was started. Required when creating a worklog. Optional when updating a worklog.
timeSpentstringNoThe time spent working on the issue as days (#d), hours (#h), or minutes (#m or #). Required when creating a worklog if timeSpentSeconds isn’t provided. Optional when updating a worklog. Cannot be provided if timeSpentSecond is provided.
timeSpentSecondsintegerNoThe time in seconds spent working on the issue. Required when creating a worklog if timeSpent isn’t provided. Optional when updating a worklog. Cannot be provided if timeSpent is provided.
updateAuthorobjectNoDetails of the user who last updated the worklog.
updatedstringNoThe datetime on which the worklog was last updated.
visibilityobjectNoDetails about any restrictions in the visibility of the worklog. Optional when creating or updating a worklog.

jira_issues_assign_issue

Assign issue Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue to be assigned.
accountIdstringNoThe account ID of the user, which uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5. Required in requests.
accountTypestringNoThe user account type. Can take the following values: * atlassian regular Atlassian user account * app system account used for Connect applications and OAuth to represent external systems * customer Jira Service Desk account representing an external service desk
activebooleanNoWhether the user is active.
applicationRolesobjectNoThe application roles the user is assigned to.
appTypestringNoThe app type of the user account when accountType is ‘app’. Can take the following values: * service Service Account * agent Rovo Agent Account * unknown Unknown app type
avatarUrlsobjectNoThe avatars of the user.
displayNamestringNoThe display name of the user. Depending on the user’s privacy setting, this may return an alternative value.
emailAddressstringNoThe email address of the user. Depending on the user’s privacy setting, this may be returned as null.
expandstringNoExpand options that include additional user details in the response.
groupsobjectNoThe groups that the user belongs to.
guestbooleanNoWhether the user is a guest.
keystringNoThis property is no longer available and will be removed from the documentation soon. See the deprecation notice for details.
localestringNoThe locale of the user. Depending on the user’s privacy setting, this may be returned as null.
namestringNoThis property is no longer available and will be removed from the documentation soon. See the deprecation notice for details.
selfstringNoThe URL of the user.
timeZonestringNoThe time zone specified in the user’s profile. If the user’s time zone is not visible to the current user (due to user’s profile setting), or if a time zone has not been set, the instance’s default time zone will be returned.

jira_issues_bulk_fetch_issues

Bulk fetch issues Parameters:
ParameterTypeRequiredDefaultDescription
expandany[]NoUse expand to include additional information about issues in the response. Note that, unlike the majority of instances where expand is specified, expand is defined as a list of values. The expand options are: * renderedFields Returns field values rendered in HTML format. * names Returns the display name of each field. * schema Returns the schema describing a field type. * transitions Returns all possible transitions for the issue. * operations Returns all possible operations for the issue. * editmeta Returns information about how each field can be edited. * changelog Returns a list of recent updates to an issue, sorted by date, starting from the most recent. This returns a maximum of 40 changelogs. If you require more, please refer to Bulk fetch changelogs. * versionedRepresentations Instead of fields, returns versionedRepresentations a JSON array containing each version of a field’s value, with the highest numbered item representing the most recent version.
fieldsany[]NoA list of fields to return for each issue, use it to retrieve a subset of fields. This parameter accepts a comma-separated list. Expand options include: * *all Returns all fields. * *navigable Returns navigable fields. * Any issue field, prefixed with a minus to exclude. The default is *navigable. Examples: * summary,comment Returns the summary and comments fields only. * -description Returns all navigable (default) fields except description. * *all,-comment Returns all fields except comments. Multiple fields parameters can be included in a request. Note: All navigable fields are returned by default. This differs from GET issue where the default is all fields.
fieldsByKeysbooleanNoReference fields by their key (rather than ID). The default is false.
issueIdsOrKeysany[]YesAn array of issue IDs or issue keys to fetch. You can mix issue IDs and keys in the same query.
propertiesany[]NoA list of issue property keys of issue properties to be included in the results. A maximum of 5 issue property keys can be specified.

jira_issues_count_issues

Count issues using JQL Parameters:
ParameterTypeRequiredDefaultDescription
jqlstringNoA JQL expression. For performance reasons, this parameter requires a bounded query. A bounded query is a query with a search restriction.

jira_issues_create_filter

Create filter Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * sharedUsers Returns the users that the filter is shared with. This includes users that can browse projects that the filter is shared with. If you don’t specify sharedUsers, then the sharedUsers object is returned but it doesn’t list any users. The list of users returned is limited to 1000, to access additional users append [start-index:end-index] to the expand request. For example, to access the next 1000 users, use ?expand=sharedUsers[1001:2000]. * subscriptions Returns the users that are subscribed to the filter. If you don’t specify subscriptions, the subscriptions object is returned but it doesn’t list any subscriptions. The list of subscriptions returned is limited to 1000, to access additional subscriptions append [start-index:end-index] to the expand request. For example, to access the next 1000 subscriptions, use ?expand=subscriptions[1001:2000].
overrideSharePermissionsbooleanNoEXPERIMENTAL: Whether share permissions are overridden to enable filters with any share permissions to be created. Available to users with Administer Jira global permission.
approximateLastUsedstringNo[Experimental] Approximate last used time. Returns the date and time when the filter was last used. Returns null if the filter hasn’t been used after tracking was enabled. For performance reasons, timestamps aren’t updated in real time and therefore may not be exactly accurate.
descriptionstringNoA description of the filter.
editPermissionsany[]NoThe groups and projects that can edit the filter.
favouritebooleanNoWhether the filter is selected as a favorite.
favouritedCountintegerNoThe count of how many users have selected this filter as a favorite, including the filter owner.
idstringNoThe unique identifier for the filter.
jqlstringNoThe JQL query for the filter. For example, project = SSP AND issuetype = Bug.
namestringYesThe name of the filter. Must be unique.
ownerobjectNoThe user who owns the filter. This is defaulted to the creator of the filter, however Jira administrators can change the owner of a shared filter in the admin settings.
searchUrlstringNoA URL to view the filter results in Jira, using the Search for issues using JQL operation with the filter’s JQL string to return the filter results. For example, https://your-domain.atlassian.net/rest/api/3/search?jql=project+%3D+SSP+AND+issuetype+%3D+Bug.
selfstringNoThe URL of the filter.
sharedUsersobjectNoA paginated list of the users that the filter is shared with. This includes users that are members of the groups or can browse the projects that the filter is shared with.
sharePermissionsany[]NoThe groups and projects that the filter is shared with.
subscriptionsobjectNoA paginated list of the users that are subscribed to the filter.
viewUrlstringNoA URL to view the filter results in Jira, using the ID of the filter. For example, https://your-domain.atlassian.net/issues/?filter=10100.

jira_issues_create_issue

Create issue Parameters:
ParameterTypeRequiredDefaultDescription
updateHistorybooleanNoWhether the project in which the issue is created is added to the user’s Recently viewed project list, as shown under Projects in Jira. When provided, the issue type and request type are added to the user’s history for a project. These values are then used to provide defaults on the issue create screen.
fieldsobjectNoList of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are required, use update. Fields included in here cannot be included in update.
historyMetadataobjectNoAdditional issue history details.
propertiesany[]NoDetails of issue properties to be add or update.
transitionobjectNoDetails of a transition. Required when performing a transition, optional when creating or editing an issue.
updateobjectNoA Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in fields.

jira_issues_delete_comment

Delete comment Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
idstringYesThe ID of the comment.

jira_issues_delete_filter

Delete filter Parameters:
ParameterTypeRequiredDefaultDescription
idintegerYesThe ID of the filter to delete.

jira_issues_delete_issue

Delete issue Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
deleteSubtasksstringNoWhether the issue’s subtasks are deleted when the issue is deleted.

jira_issues_delete_worklog

Delete worklog Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
idstringYesThe ID of the worklog.
notifyUsersbooleanNoWhether users watching the issue are notified by email.
adjustEstimatestringNoDefines how to update the issue’s time estimate, the options are: * new Sets the estimate to a specific value, defined in newEstimate. * leave Leaves the estimate unchanged. * manual Increases the estimate by amount specified in increaseBy. * auto Reduces the estimate by the value of timeSpent in the worklog.
newEstimatestringNoThe value to set as the issue’s remaining time estimate, as days (#d), hours (#h), or minutes (#m or #). For example, 2d. Required when adjustEstimate is new.
increaseBystringNoThe amount to increase the issue’s remaining estimate by, as days (#d), hours (#h), or minutes (#m or #). For example, 2d. Required when adjustEstimate is manual.
overrideEditableFlagbooleanNoWhether the work log entry should be added to the issue even if the issue is not editable, because jira.issue.editable set to false or missing. For example, the issue is closed. Connect and Forge app users with admin permission can use this flag.

jira_issues_do_transition

Transition issue Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
fieldsobjectNoList of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are required, use update. Fields included in here cannot be included in update.
historyMetadataobjectNoAdditional issue history details.
propertiesany[]NoDetails of issue properties to be add or update.
transitionobjectNoDetails of a transition. Required when performing a transition, optional when creating or editing an issue.
updateobjectNoA Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in fields.

jira_issues_edit_issue

Edit issue Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
notifyUsersbooleanNoWhether a notification email about the issue update is sent to all watchers. To disable the notification, administer Jira or administer project permissions are required. If the user doesn’t have the necessary permission the request is ignored.
overrideScreenSecuritybooleanNoWhether screen security is overridden to enable hidden fields to be edited. Available to Connect and Forge app users with Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.
overrideEditableFlagbooleanNoWhether screen security is overridden to enable uneditable fields to be edited. Available to Connect and Forge app users with Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.
returnIssuebooleanNoWhether the response should contain the issue with fields edited in this request. The returned issue will have the same format as in the Get issue API.
expandstringNoThe Get issue API expand parameter to use in the response if the returnIssue parameter is true.
fieldsobjectNoList of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are required, use update. Fields included in here cannot be included in update.
historyMetadataobjectNoAdditional issue history details.
propertiesany[]NoDetails of issue properties to be add or update.
transitionobjectNoDetails of a transition. Required when performing a transition, optional when creating or editing an issue.
updateobjectNoA Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in fields.

jira_issues_get_all_labels

Get all labels Parameters:
ParameterTypeRequiredDefaultDescription
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.

jira_issues_get_attachment

Get attachment metadata Parameters:
ParameterTypeRequiredDefaultDescription
idstringYesThe ID of the attachment.

jira_issues_get_attachment_meta

Get Jira attachment settings

jira_issues_get_auto_complete_post

Get field reference data (POST) Parameters:
ParameterTypeRequiredDefaultDescription
includeCollapsedFieldsbooleanNoInclude collapsed fields for fields that have non-unique names.
projectIdsany[]NoList of project IDs used to filter the visible field details returned.

jira_issues_get_comment

Get comment Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
idstringYesThe ID of the comment.
expandstringNoUse expand to include additional information about comments in the response. This parameter accepts renderedBody, which returns the comment body rendered in HTML.

jira_issues_get_comments

Get comments Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.
orderBystringNoOrder the results by a field. Accepts created to sort comments by their created date.
expandstringNoUse expand to include additional information about comments in the response. This parameter accepts renderedBody, which returns the comment body rendered in HTML.

jira_issues_get_create_issue_meta_issue_type_id

Get create field metadata for a project and issue type id Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe ID or key of the project.
issueTypeIdstringYesThe issuetype ID.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.

jira_issues_get_create_issue_meta_issue_types

Get create metadata issue types for a project Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe ID or key of the project.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.

jira_issues_get_edit_issue_meta

Get edit issue metadata Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
overrideScreenSecuritybooleanNoWhether hidden fields are returned. Available to Connect and Forge app users with Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.
overrideEditableFlagbooleanNoWhether non-editable fields are returned. Available to Connect and Forge app users with Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.

jira_issues_get_favourite_filters

Get favorite filters Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * sharedUsers Returns the users that the filter is shared with. This includes users that can browse projects that the filter is shared with. If you don’t specify sharedUsers, then the sharedUsers object is returned but it doesn’t list any users. The list of users returned is limited to 1000, to access additional users append [start-index:end-index] to the expand request. For example, to access the next 1000 users, use ?expand=sharedUsers[1001:2000]. * subscriptions Returns the users that are subscribed to the filter. If you don’t specify subscriptions, the subscriptions object is returned but it doesn’t list any subscriptions. The list of subscriptions returned is limited to 1000, to access additional subscriptions append [start-index:end-index] to the expand request. For example, to access the next 1000 subscriptions, use ?expand=subscriptions[1001:2000].

jira_issues_get_filter

Get filter Parameters:
ParameterTypeRequiredDefaultDescription
idintegerYesThe ID of the filter to return.
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * sharedUsers Returns the users that the filter is shared with. This includes users that can browse projects that the filter is shared with. If you don’t specify sharedUsers, then the sharedUsers object is returned but it doesn’t list any users. The list of users returned is limited to 1000, to access additional users append [start-index:end-index] to the expand request. For example, to access the next 1000 users, use ?expand=sharedUsers[1001:2000]. * subscriptions Returns the users that are subscribed to the filter. If you don’t specify subscriptions, the subscriptions object is returned but it doesn’t list any subscriptions. The list of subscriptions returned is limited to 1000, to access additional subscriptions append [start-index:end-index] to the expand request. For example, to access the next 1000 subscriptions, use ?expand=subscriptions[1001:2000].
overrideSharePermissionsbooleanNoEXPERIMENTAL: Whether share permissions are overridden to enable filters with any share permissions to be returned. Available to users with Administer Jira global permission.

jira_issues_get_filters_paginated

Search for filters Parameters:
ParameterTypeRequiredDefaultDescription
filterNamestringNoString used to perform a case-insensitive partial match with name.
accountIdstringNoUser account ID used to return filters with the matching owner.accountId. This parameter cannot be used with owner.
ownerstringNoThis parameter is deprecated because of privacy changes. Use accountId instead. See the migration guide for details. User name used to return filters with the matching owner.name. This parameter cannot be used with accountId.
groupnamestringNoAs a group’s name can change, use of groupId is recommended to identify a group. Group name used to returns filters that are shared with a group that matches sharePermissions.group.groupname. This parameter cannot be used with the groupId parameter.
groupIdstringNoGroup ID used to returns filters that are shared with a group that matches sharePermissions.group.groupId. This parameter cannot be used with the groupname parameter.
projectIdintegerNoProject ID used to returns filters that are shared with a project that matches sharePermissions.project.id.
idany[]NoThe list of filter IDs. To include multiple IDs, provide an ampersand-separated list. For example, id=10000&id=10001. Do not exceed 200 filter IDs.
orderBystringNoOrder the results by a field: * description Sorts by filter description. Note that this sorting works independently of whether the expand to display the description field is in use. * favourite_count Sorts by the count of how many users have this filter as a favorite. * is_favourite Sorts by whether the filter is marked as a favorite. * id Sorts by filter ID. * name Sorts by filter name. * owner Sorts by the ID of the filter owner. * is_shared Sorts by whether the filter is shared.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * description Returns the description of the filter. * favourite Returns an indicator of whether the user has set the filter as a favorite. * favouritedCount Returns a count of how many users have set this filter as a favorite. * jql Returns the JQL query that the filter uses. * owner Returns the owner of the filter. * searchUrl Returns a URL to perform the filter’s JQL query. * sharePermissions Returns the share permissions defined for the filter. * editPermissions Returns the edit permissions defined for the filter. * isWritable Returns whether the current user has permission to edit the filter. * approximateLastUsed [Experimental] Returns the approximate date and time when the filter was last evaluated. * subscriptions Returns the users that are subscribed to the filter. * viewUrl Returns a URL to view the filter.
overrideSharePermissionsbooleanNoEXPERIMENTAL: Whether share permissions are overridden to enable filters with any share permissions to be returned. Available to users with Administer Jira global permission.
isSubstringMatchbooleanNoWhen true this will perform a case-insensitive substring match for the provided filterName. When false the filter name will be searched using full text search syntax.

jira_issues_get_issue

Get issue Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
fieldsany[]NoA list of fields to return for the issue. This parameter accepts a comma-separated list. Use it to retrieve a subset of fields. Allowed values: * *all Returns all fields. * *navigable Returns navigable fields. * Any issue field, prefixed with a minus to exclude. Examples: * summary,comment Returns only the summary and comments fields. * -description Returns all (default) fields except description. * *navigable,-comment Returns all navigable fields except comment. This parameter may be specified multiple times. For example, fields=field1,field2& fields=field3. Note: All fields are returned by default. This differs from Search for issues using JQL (GET) and Search for issues using JQL (POST) where the default is all navigable fields.
fieldsByKeysbooleanNoWhether fields in fields are referenced by keys rather than IDs. This parameter is useful where fields have been added by a connect app and a field’s key may differ from its ID.
expandstringNoUse expand to include additional information about the issues in the response. This parameter accepts a comma-separated list. Expand options include: * renderedFields Returns field values rendered in HTML format. * names Returns the display name of each field. * schema Returns the schema describing a field type. * transitions Returns all possible transitions for the issue. * editmeta Returns information about how each field can be edited. * changelog Returns a list of recent updates to an issue, sorted by date, starting from the most recent. * versionedRepresentations Returns a JSON array for each version of a field’s value, with the highest number representing the most recent version. Note: When included in the request, the fields parameter is ignored.
propertiesany[]NoA list of issue properties to return for the issue. This parameter accepts a comma-separated list. Allowed values: * *all Returns all issue properties. * Any issue property key, prefixed with a minus to exclude. Examples: * *all Returns all properties. * *all,-prop1 Returns all properties except prop1. * prop1,prop2 Returns prop1 and prop2 properties. This parameter may be specified multiple times. For example, properties=prop1,prop2& properties=prop3.
updateHistorybooleanNoWhether the project in which the issue is created is added to the user’s Recently viewed project list, as shown under Projects in Jira. This also populates the JQL issues search lastViewed field.
failFastbooleanNoWhether to fail the request quickly in case of an error while loading fields for an issue. For failFast=true, if one field fails, the entire operation fails. For failFast=false, the operation will continue even if a field fails. It will return a valid response, but without values for the failed field(s).

Get issue link Parameters:
ParameterTypeRequiredDefaultDescription
linkIdstringYesThe ID of the issue link.

Get issue link types

jira_issues_get_issue_watchers

Get issue watchers Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.

jira_issues_get_my_filters

Get my filters Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * sharedUsers Returns the users that the filter is shared with. This includes users that can browse projects that the filter is shared with. If you don’t specify sharedUsers, then the sharedUsers object is returned but it doesn’t list any users. The list of users returned is limited to 1000, to access additional users append [start-index:end-index] to the expand request. For example, to access the next 1000 users, use ?expand=sharedUsers[1001:2000]. * subscriptions Returns the users that are subscribed to the filter. If you don’t specify subscriptions, the subscriptions object is returned but it doesn’t list any subscriptions. The list of subscriptions returned is limited to 1000, to access additional subscriptions append [start-index:end-index] to the expand request. For example, to access the next 1000 subscriptions, use ?expand=subscriptions[1001:2000].
includeFavouritesbooleanNoInclude the user’s favorite filters in the response.

jira_issues_get_transitions

Get transitions Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
expandstringNoUse expand to include additional information about transitions in the response. This parameter accepts transitions.fields, which returns information about the fields in the transition screen for each transition. Fields hidden from the screen are not returned. Use this information to populate the fields and update fields in Transition issue.
transitionIdstringNoThe ID of the transition.
skipRemoteOnlyConditionbooleanNoWhether transitions with the condition Hide From User Condition are included in the response. Available to Connect and Forge app users with Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.
includeUnavailableTransitionsbooleanNoWhether details of transitions that fail a condition are included in the response
sortByOpsBarAndStatusbooleanNoWhether the transitions are sorted by ops-bar sequence value first then category order (Todo, In Progress, Done) or only by ops-bar sequence value.

jira_issues_get_votes

Get votes Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.

jira_issues_get_worklog

Get worklog Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
idstringYesThe ID of the worklog.
expandstringNoUse expand to include additional information about work logs in the response. This parameter accepts properties, which returns worklog properties.

Create issue link Parameters:
ParameterTypeRequiredDefaultDescription
commentobjectNoA comment.
inwardIssueobjectYesThe ID or key of a linked issue.
outwardIssueobjectYesThe ID or key of a linked issue.
typeobjectYesThis object is used as follows: * In the issueLink resource it defines and reports on the type of link between the issues. Find a list of issue link types with Get issue link types. * In the issueLinkType resource it defines and reports on issue link types.

jira_issues_remove_vote

Delete vote Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.

jira_issues_remove_watcher

Delete watcher Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
usernamestringNoThis parameter is no longer available. See the deprecation notice for details.
accountIdstringNoThe account ID of the user, which uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5. Required.

jira_issues_search_and_reconsile_issues_using_jql_post

Search for issues using JQL enhanced search (POST) Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information about issues in the response. Note that, unlike the majority of instances where expand is specified, expand is defined as a comma-delimited string of values. The expand options are: * renderedFields Returns field values rendered in HTML format. * names Returns the display name of each field. * schema Returns the schema describing a field type. * transitions Returns all possible transitions for the issue. * operations Returns all possible operations for the issue. * editmeta Returns information about how each field can be edited. * changelog Returns a list of recent updates to an issue, sorted by date, starting from the most recent. * versionedRepresentations Instead of fields, returns versionedRepresentations a JSON array containing each version of a field’s value, with the highest numbered item representing the most recent version. Examples: "names,changelog" Returns the display name of each field as well as a list of recent updates to an issue.
fieldsany[]NoA list of fields to return for each issue. Use it to retrieve a subset of fields. This parameter accepts a comma-separated list. Expand options include: * *all Returns all fields. * *navigable Returns navigable fields. * id Returns only issue IDs. * Any issue field, prefixed with a dash to exclude. The default is id. Examples: * summary,comment Returns the summary and comments fields only. * *all,-comment Returns all fields except comments. Multiple fields parameters can be included in a request. Note: By default, this resource returns IDs only. This differs from GET issue where the default is all fields.
fieldsByKeysbooleanNoReference fields by their key (rather than ID). The default is false.
jqlstringNoA JQL expression. For performance reasons, this parameter requires a bounded query. A bounded query is a query with a search restriction. * Example of an unbounded query: order by key desc. * Example of a bounded query: assignee = currentUser() order by key. Additionally, orderBy clause can contain a maximum of 7 fields.
maxResultsintegerNoThe maximum number of items to return per page. To manage page size, API may return fewer items per page where a large number of fields are requested. The greatest number of items returned per page is achieved when requesting id or key only. It returns max 5000 issues.
nextPageTokenstringNoThe token for a page to fetch that is not the first page. The first page has a nextPageToken of null. Use the nextPageToken to fetch the next page of issues.
propertiesany[]NoA list of up to 5 issue properties to include in the results. This parameter accepts a comma-separated list.
reconcileIssuesany[]NoStrong consistency issue ids to be reconciled with search results. Accepts max 50 ids. This list of ids should be consistent with each paginated request across different pages.

jira_issues_update_comment

Update comment Parameters:
ParameterTypeRequiredDefaultDescription
issueIdOrKeystringYesThe ID or key of the issue.
idstringYesThe ID of the comment.
notifyUsersbooleanNoWhether users are notified when a comment is updated.
overrideEditableFlagbooleanNoWhether screen security is overridden to enable uneditable fields to be edited. Available to Connect app users with the Administer Jira global permission and Forge apps acting on behalf of users with Administer Jira global permission.
expandstringNoUse expand to include additional information about comments in the response. This parameter accepts renderedBody, which returns the comment body rendered in HTML.
authorobjectNoThe ID of the user who created the comment.
bodyobjectNoThe comment text in Atlassian Document Format.
createdstringNoThe date and time at which the comment was created.
jsdAuthorCanSeeRequestbooleanNoWhether the comment was added from an email sent by a person who is not part of the issue. See Allow external emails to be added as comments on issuesfor information on setting up this feature.
jsdPublicbooleanNoWhether the comment is visible in Jira Service Desk. Defaults to true when comments are created in the Jira Cloud Platform. This includes when the site doesn’t use Jira Service Desk or the project isn’t a Jira Service Desk project and, therefore, there is no Jira Service Desk for the issue to be visible on. To create a comment with its visibility in Jira Service Desk set to false, use the Jira Service Desk REST API Create request comment operation.
propertiesany[]NoA list of comment properties. Optional on create and update.
renderedBodystringNoThe rendered version of the comment.
selfstringNoThe URL of the comment.
updateAuthorobjectNoThe ID of the user who updated the comment last.
updatedstringNoThe date and time at which the comment was updated last.
visibilityobjectNoThe group or role to which this comment is visible. Optional on create and update.

jira_issues_update_filter

Update filter Parameters:
ParameterTypeRequiredDefaultDescription
idintegerYesThe ID of the filter to update.
expandstringNoUse expand to include additional information about filter in the response. This parameter accepts a comma-separated list. Expand options include: * sharedUsers Returns the users that the filter is shared with. This includes users that can browse projects that the filter is shared with. If you don’t specify sharedUsers, then the sharedUsers object is returned but it doesn’t list any users. The list of users returned is limited to 1000, to access additional users append [start-index:end-index] to the expand request. For example, to access the next 1000 users, use ?expand=sharedUsers[1001:2000]. * subscriptions Returns the users that are subscribed to the filter. If you don’t specify subscriptions, the subscriptions object is returned but it doesn’t list any subscriptions. The list of subscriptions returned is limited to 1000, to access additional subscriptions append [start-index:end-index] to the expand request. For example, to access the next 1000 subscriptions, use ?expand=subscriptions[1001:2000].
overrideSharePermissionsbooleanNoEXPERIMENTAL: Whether share permissions are overridden to enable the addition of any share permissions to filters. Available to users with Administer Jira global permission.
approximateLastUsedstringNo[Experimental] Approximate last used time. Returns the date and time when the filter was last used. Returns null if the filter hasn’t been used after tracking was enabled. For performance reasons, timestamps aren’t updated in real time and therefore may not be exactly accurate.
descriptionstringNoA description of the filter.
editPermissionsany[]NoThe groups and projects that can edit the filter.
favouritebooleanNoWhether the filter is selected as a favorite.
favouritedCountintegerNoThe count of how many users have selected this filter as a favorite, including the filter owner.
jqlstringNoThe JQL query for the filter. For example, project = SSP AND issuetype = Bug.
namestringYesThe name of the filter. Must be unique.
ownerobjectNoThe user who owns the filter. This is defaulted to the creator of the filter, however Jira administrators can change the owner of a shared filter in the admin settings.
searchUrlstringNoA URL to view the filter results in Jira, using the Search for issues using JQL operation with the filter’s JQL string to return the filter results. For example, https://your-domain.atlassian.net/rest/api/3/search?jql=project+%3D+SSP+AND+issuetype+%3D+Bug.
selfstringNoThe URL of the filter.
sharedUsersobjectNoA paginated list of the users that the filter is shared with. This includes users that are members of the groups or can browse the projects that the filter is shared with.
sharePermissionsany[]NoThe groups and projects that the filter is shared with.
subscriptionsobjectNoA paginated list of the users that are subscribed to the filter.
viewUrlstringNoA URL to view the filter results in Jira, using the ID of the filter. For example, https://your-domain.atlassian.net/issues/?filter=10100.

jira-projects

Jira Projects - browse projects, components, versions, statuses, categories, and dashboards Server path: /jira-projects | Type: Application | PCID required: Yes

Tools


jira_projects_create_component

Create component Parameters:
ParameterTypeRequiredDefaultDescription
aristringNoCompass component’s ID. Can’t be updated. Not required for creating a Project Component.
assigneeobjectNoThe details of the user associated with assigneeType, if any. See realAssignee for details of the user assigned to issues created with this component.
assigneeTypestringNoThe nominal user type used to determine the assignee for issues created with this component. See realAssigneeType for details on how the type of the user, and hence the user, assigned to issues is determined. Can take the following values: * PROJECT_LEAD the assignee to any issues created with this component is nominally the lead for the project the component is in. * COMPONENT_LEAD the assignee to any issues created with this component is nominally the lead for the component. * UNASSIGNED an assignee is not set for issues created with this component. * PROJECT_DEFAULT the assignee to any issues created with this component is nominally the default assignee for the project that the component is in. Default value: PROJECT_DEFAULT. Optional when creating or updating a component.
descriptionstringNoThe description for the component. Optional when creating or updating a component.
idstringNoThe unique identifier for the component.
isAssigneeTypeValidbooleanNoWhether a user is associated with assigneeType. For example, if the assigneeType is set to COMPONENT_LEAD but the component lead is not set, then false is returned.
leadobjectNoThe user details for the component’s lead user.
leadAccountIdstringNoThe accountId of the component’s lead user. The accountId uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5.
leadUserNamestringNoThis property is no longer available and will be removed from the documentation soon. See the deprecation notice for details.
metadataobjectNoCompass component’s metadata. Can’t be updated. Not required for creating a Project Component.
namestringNoThe unique name for the component in the project. Required when creating a component. Optional when updating a component. The maximum length is 255 characters.
projectstringNoThe key of the project the component is assigned to. Required when creating a component. Can’t be updated.
projectIdintegerNoThe ID of the project the component is assigned to.
realAssigneeobjectNoThe user assigned to issues created with this component, when assigneeType does not identify a valid assignee.
realAssigneeTypestringNoThe type of the assignee that is assigned to issues created with this component, when an assignee cannot be set from the assigneeType. For example, assigneeType is set to COMPONENT_LEAD but no component lead is set. This property is set to one of the following values: * PROJECT_LEAD when assigneeType is PROJECT_LEAD and the project lead has permission to be assigned issues in the project that the component is in. * COMPONENT_LEAD when assigneeType is COMPONENT_LEAD and the component lead has permission to be assigned issues in the project that the component is in. * UNASSIGNED when assigneeType is UNASSIGNED and Jira is configured to allow unassigned issues. * PROJECT_DEFAULT when none of the preceding cases are true.
selfstringNoThe URL of the component.

jira_projects_create_version

Create version Parameters:
ParameterTypeRequiredDefaultDescription
approversany[]NoIf the expand option approvers is used, returns a list containing the approvers for this version.
archivedbooleanNoIndicates that the version is archived. Optional when creating or updating a version.
descriptionstringNoThe description of the version. Optional when creating or updating a version. The maximum size is 16,384 bytes.
driverstringNoIf the expand option driver is used, returns the Atlassian account ID of the driver.
expandstringNoUse expand to include additional information about version in the response. This parameter accepts a comma-separated list. Expand options include: * operations Returns the list of operations available for this version. * issuesstatus Returns the count of issues in this version for each of the status categories to do, in progress, done, and unmapped. The unmapped property contains a count of issues with a status other than to do, in progress, and done. * driver Returns the Atlassian account ID of the version driver. * approvers Returns a list containing approvers for this version. Optional for create and update.
idstringNoThe ID of the version.
issuesStatusForFixVersionobjectNoIf the expand option issuesstatus is used, returns the count of issues in this version for each of the status categories to do, in progress, done, and unmapped. The unmapped property contains a count of issues with a status other than to do, in progress, and done.
moveUnfixedIssuesTostringNoThe URL of the self link to the version to which all unfixed issues are moved when a version is released. Not applicable when creating a version. Optional when updating a version.
namestringNoThe unique name of the version. Required when creating a version. Optional when updating a version. The maximum length is 255 characters.
operationsany[]NoIf the expand option operations is used, returns the list of operations available for this version.
overduebooleanNoIndicates that the version is overdue.
projectstringNoDeprecated. Use projectId.
projectIdintegerNoThe ID of the project to which this version is attached. Required when creating a version. Not applicable when updating a version.
releasedbooleanNoIndicates that the version is released. If the version is released a request to release again is ignored. Not applicable when creating a version. Optional when updating a version.
releaseDatestringNoThe release date of the version. Expressed in ISO 8601 format (yyyy-mm-dd). Optional when creating or updating a version.
selfstringNoThe URL of the version.
startDatestringNoThe start date of the version. Expressed in ISO 8601 format (yyyy-mm-dd). Optional when creating or updating a version.
userReleaseDatestringNoThe date on which work on this version is expected to finish, expressed in the instance’s Day/Month/Year Format date format.
userStartDatestringNoThe date on which work on this version is expected to start, expressed in the instance’s Day/Month/Year Format date format.

jira_projects_get_all_available_dashboard_gadgets

Get available gadgets

jira_projects_get_all_gadgets

Get gadgets Parameters:
ParameterTypeRequiredDefaultDescription
dashboardIdintegerYesThe ID of the dashboard.
moduleKeyany[]NoThe list of gadgets module keys. To include multiple module keys, separate module keys with ampersand: moduleKey=key:one&moduleKey=key:two.
uriany[]NoThe list of gadgets URIs. To include multiple URIs, separate URIs with ampersand: uri=/rest/example/uri/1&uri=/rest/example/uri/2.
gadgetIdany[]NoThe list of gadgets IDs. To include multiple IDs, separate IDs with ampersand: gadgetId=10000&gadgetId=10001.

jira_projects_get_all_project_categories

Get all project categories

jira_projects_get_all_statuses

Get all statuses for project Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe project ID or project key (case sensitive).

jira_projects_get_component

Get component Parameters:
ParameterTypeRequiredDefaultDescription
idstringYesThe ID of the component.

jira_projects_get_dashboard

Get dashboard Parameters:
ParameterTypeRequiredDefaultDescription
idstringYesThe ID of the dashboard.

jira_projects_get_dashboards_paginated

Search for dashboards Parameters:
ParameterTypeRequiredDefaultDescription
dashboardNamestringNoString used to perform a case-insensitive partial match with name.
accountIdstringNoUser account ID used to return dashboards with the matching owner.accountId. This parameter cannot be used with the owner parameter.
ownerstringNoThis parameter is deprecated because of privacy changes. Use accountId instead. See the migration guide for details. User name used to return dashboards with the matching owner.name. This parameter cannot be used with the accountId parameter.
groupnamestringNoAs a group’s name can change, use of groupId is recommended. Group name used to return dashboards that are shared with a group that matches sharePermissions.group.name. This parameter cannot be used with the groupId parameter.
groupIdstringNoGroup ID used to return dashboards that are shared with a group that matches sharePermissions.group.groupId. This parameter cannot be used with the groupname parameter.
projectIdintegerNoProject ID used to returns dashboards that are shared with a project that matches sharePermissions.project.id.
orderBystringNoOrder the results by a field: * description Sorts by dashboard description. Note that this sort works independently of whether the expand to display the description field is in use. * favourite_count Sorts by dashboard popularity. * id Sorts by dashboard ID. * is_favourite Sorts by whether the dashboard is marked as a favorite. * name Sorts by dashboard name. * owner Sorts by dashboard owner name.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.
statusstringNoThe status to filter by. It may be active, archived or deleted.
expandstringNoUse expand to include additional information about dashboard in the response. This parameter accepts a comma-separated list. Expand options include: * description Returns the description of the dashboard. * owner Returns the owner of the dashboard. * viewUrl Returns the URL that is used to view the dashboard. * favourite Returns isFavourite, an indicator of whether the user has set the dashboard as a favorite. * favouritedCount Returns popularity, a count of how many users have set this dashboard as a favorite. * sharePermissions Returns details of the share permissions defined for the dashboard. * editPermissions Returns details of the edit permissions defined for the dashboard. * isWritable Returns whether the current user has permission to edit the dashboard.

jira_projects_get_project

Get project Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe project ID or project key (case sensitive).
expandstringNoUse expand to include additional information in the response. This parameter accepts a comma-separated list. Note that the project description, issue types, and project lead are included in all responses by default. Expand options include: * description The project description. * issueTypes The issue types associated with the project. * lead The project lead. * projectKeys All project keys associated with the project. * issueTypeHierarchy The project issue type hierarchy.
propertiesany[]NoA list of project properties to return for the project. This parameter accepts a comma-separated list.

jira_projects_get_project_components

Get project components Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe project ID or project key (case sensitive).
componentSourcestringNoThe source of the components to return. Can be jira (default), compass or auto. When auto is specified, the API will return connected Compass components if the project is opted into Compass, otherwise it will return Jira components. Defaults to jira.

jira_projects_get_project_versions_paginated

Get project versions paginated Parameters:
ParameterTypeRequiredDefaultDescription
projectIdOrKeystringYesThe project ID or project key (case sensitive).
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.
orderBystringNoOrder the results by a field: * description Sorts by version description. * name Sorts by version name. * releaseDate Sorts by release date, starting with the oldest date. Versions with no release date are listed last. * sequence Sorts by the order of appearance in the user interface. * startDate Sorts by start date, starting with the oldest date. Versions with no start date are listed last.
querystringNoFilter the results using a literal string. Versions with matching name or description are returned (case insensitive).
statusstringNoA list of status values used to filter the results by version status. This parameter accepts a comma-separated list. The status values are released, unreleased, and archived.
expandstringNoUse expand to include additional information in the response. This parameter accepts a comma-separated list. Expand options include: * issuesstatus Returns the number of issues in each status category for each version. * operations Returns actions that can be performed on the specified version. * driver Returns the Atlassian account ID of the version driver. * approvers Returns a list containing the approvers for this version.

jira_projects_get_recent

Get recent projects Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information in the response. This parameter accepts a comma-separated list. Expanded options include: * description Returns the project description. * projectKeys Returns all project keys associated with a project. * lead Returns information about the project lead. * issueTypes Returns all issue types associated with the project. * url Returns the URL associated with the project. * permissions Returns the permissions associated with the project. * insight EXPERIMENTAL. Returns the insight details of total issue count and last issue update time for the project. * * Returns the project with all available expand options.
propertiesany[]NoEXPERIMENTAL. A list of project properties to return for the project. This parameter accepts a comma-separated list. Invalid property names are ignored.

jira_projects_get_status_categories

Get all status categories

jira_projects_get_status_category

Get status category Parameters:
ParameterTypeRequiredDefaultDescription
idOrKeystringYesThe ID or key of the status category.

jira_projects_get_statuses

Get all statuses

jira_projects_get_version

Get version Parameters:
ParameterTypeRequiredDefaultDescription
idstringYesThe ID of the version.
expandstringNoUse expand to include additional information about version in the response. This parameter accepts a comma-separated list. Expand options include: * operations Returns the list of operations available for this version. * issuesstatus Returns the count of issues in this version for each of the status categories to do, in progress, done, and unmapped. The unmapped property represents the number of issues with a status other than to do, in progress, and done. * driver Returns the Atlassian account ID of the version driver. * approvers Returns a list containing the Atlassian account IDs of approvers for this version.

jira_projects_search_projects

Get projects paginated Parameters:
ParameterTypeRequiredDefaultDescription
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return per page. Must be less than or equal to 100. If a value greater than 100 is provided, the maxResults parameter will default to 100.
orderBystringNoOrder the results by a field. * category Sorts by project category. A complete list of category IDs is found using Get all project categories. * issueCount Sorts by the total number of issues in each project. * key Sorts by project key. * lastIssueUpdatedTime Sorts by the last issue update time. * name Sorts by project name. * owner Sorts by project lead. * archivedDate EXPERIMENTAL. Sorts by project archived date. * deletedDate EXPERIMENTAL. Sorts by project deleted date.
idany[]NoThe project IDs to filter the results by. To include multiple IDs, provide an ampersand-separated list. For example, id=10000&id=10001. Up to 50 project IDs can be provided.
keysany[]NoThe project keys to filter the results by. To include multiple keys, provide an ampersand-separated list. For example, keys=PA&keys=PB. Up to 50 project keys can be provided.
querystringNoFilter the results using a literal string. Projects with a matching key or name are returned (case insensitive).
typeKeystringNoOrders results by the project type. This parameter accepts a comma-separated list. Valid values are business, service_desk, and software.
categoryIdintegerNoThe ID of the project’s category. A complete list of category IDs is found using the Get all project categories operation.
actionstringNoFilter results by projects for which the user can: * view the project, meaning that they have one of the following permissions: * Browse projects project permission for the project. * Administer projects project permission for the project. * Administer Jira global permission. * browse the project, meaning that they have the Browse projects project permission for the project. * edit the project, meaning that they have one of the following permissions: * Administer projects project permission for the project. * Administer Jira global permission. * create the project, meaning that they have the Create issues project permission for the project in which the issue is created.
expandstringNoUse expand to include additional information in the response. This parameter accepts a comma-separated list. Expanded options include: * description Returns the project description. * projectKeys Returns all project keys associated with a project. * lead Returns information about the project lead. * issueTypes Returns all issue types associated with the project. * url Returns the URL associated with the project. * insight EXPERIMENTAL. Returns the insight details of total issue count and last issue update time for the project.
statusany[]NoEXPERIMENTAL. Filter results by project status: * live Search live projects. * archived Search archived projects. * deleted Search deleted projects, those in the recycle bin.
propertiesany[]NoEXPERIMENTAL. A list of project properties to return for the project. This parameter accepts a comma-separated list.
propertyQuerystringNoEXPERIMENTAL. A query string used to search properties. The query string cannot be specified using a JSON object. For example, to search for the value of nested from {"something":{"nested":1,"other":2}} use [thepropertykey].something.nested=1. Note that the propertyQuery key is enclosed in square brackets to enable searching where the propertyQuery key includes dot (.) or equals (=) characters. Note that thepropertykey is only returned when included in properties.

jira-users

Jira Users - find and look up users, groups, and permissions Server path: /jira-users | Type: Application | PCID required: Yes

Tools

ToolDescription
jira_users_find_assignable_usersFind users assignable to issues
jira_users_find_usersFind users
jira_users_find_users_and_groupsFind users and groups
jira_users_find_users_for_pickerFind users for picker
jira_users_get_bulk_permissionsGet bulk permissions
jira_users_get_current_userGet current user
jira_users_get_my_permissionsGet my permissions
jira_users_get_userGet user

jira_users_find_assignable_users

Find users assignable to issues Parameters:
ParameterTypeRequiredDefaultDescription
querystringNoA query string that is matched against user attributes, such as displayName, and emailAddress, to find relevant users. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com. Required, unless username or accountId is specified.
sessionIdstringNoThe sessionId of this request. SessionId is the same until the assignee is set.
usernamestringNoThis parameter is no longer available. See the deprecation notice for details.
accountIdstringNoA query string that is matched exactly against user accountId. Required, unless query is specified.
projectstringNoThe project ID or project key (case sensitive). Required, unless issueKey or issueId is specified.
issueKeystringNoThe key of the issue. Required, unless issueId or project is specified.
issueIdstringNoThe ID of the issue. Required, unless issueKey or project is specified.
startAtintegerNoThe index of the first item to return in a page of results (page offset).
maxResultsintegerNoThe maximum number of items to return. This operation may return less than the maximum number of items even if more are available. The operation fetches users up to the maximum and then, from the fetched users, returns only the users that can be assigned to the issue.
actionDescriptorIdintegerNoThe ID of the transition.
recommendbooleanNorecommend
accountTypeany[]NoaccountType
appTypeany[]NoappType

jira_users_find_users

Find users Parameters:
ParameterTypeRequiredDefaultDescription
querystringNoA query string that is matched against user attributes ( displayName, and emailAddress) to find relevant users. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com. Required, unless accountId or property is specified.
usernamestringNousername
accountIdstringNoA query string that is matched exactly against a user accountId. Required, unless query or property is specified.
startAtintegerNoThe index of the first item to return in a page of filtered results (page offset).
maxResultsintegerNoThe maximum number of items to return per page.
propertystringNoA query string used to search properties. Property keys are specified by path, so property keys containing dot (.) or equals (=) characters cannot be used. The query string cannot be specified using a JSON object. Example: To search for the value of nested from {"something":{"nested":1,"other":2}} use thepropertykey.something.nested=1. Required, unless accountId or query is specified.

jira_users_find_users_and_groups

Find users and groups Parameters:
ParameterTypeRequiredDefaultDescription
querystringYesThe search string.
maxResultsintegerNoThe maximum number of items to return in each list.
showAvatarbooleanNoWhether the user avatar should be returned. If an invalid value is provided, the default value is used.
fieldIdstringNoThe custom field ID of the field this request is for.
projectIdany[]NoThe ID of a project that returned users and groups must have permission to view. To include multiple projects, provide an ampersand-separated list. For example, projectId=10000&projectId=10001. This parameter is only used when fieldId is present.
issueTypeIdany[]NoThe ID of an issue type that returned users and groups must have permission to view. To include multiple issue types, provide an ampersand-separated list. For example, issueTypeId=10000&issueTypeId=10001. Special values, such as -1 (all standard issue types) and -2 (all subtask issue types), are supported. This parameter is only used when fieldId is present.
avatarSizestringNoThe size of the avatar to return. If an invalid value is provided, the default value is used.
caseInsensitivebooleanNoWhether the search for groups should be case insensitive.
excludeConnectAddonsbooleanNoWhether Connect app users and groups should be excluded from the search results. If an invalid value is provided, the default value is used.

jira_users_find_users_for_picker

Find users for picker Parameters:
ParameterTypeRequiredDefaultDescription
querystringYesA query string that is matched against user attributes, such as displayName, and emailAddress, to find relevant users. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com.
maxResultsintegerNoThe maximum number of items to return. The total number of matched users is returned in total.
showAvatarbooleanNoInclude the URI to the user’s avatar.
excludeany[]NoThis parameter is no longer available. See the deprecation notice for details.
excludeAccountIdsany[]NoA list of account IDs to exclude from the search results. This parameter accepts a comma-separated list. Multiple account IDs can also be provided using an ampersand-separated list. For example, excludeAccountIds=5b10a2844c20165700ede21g,5b10a0effa615349cb016cd8&excludeAccountIds=5b10ac8d82e05b22cc7d4ef5. Cannot be provided with exclude.
avatarSizestringNoavatarSize
excludeConnectUsersbooleanNoexcludeConnectUsers

jira_users_get_bulk_permissions

Get bulk permissions Parameters:
ParameterTypeRequiredDefaultDescription
accountIdstringNoThe account ID of a user.
globalPermissionsany[]NoGlobal permissions to look up.
projectPermissionsany[]NoProject permissions with associated projects and issues to look up.

jira_users_get_current_user

Get current user Parameters:
ParameterTypeRequiredDefaultDescription
expandstringNoUse expand to include additional information about user in the response. This parameter accepts a comma-separated list. Expand options include: * groups Returns all groups, including nested groups, the user belongs to. * applicationRoles Returns the application roles the user is assigned to.

jira_users_get_my_permissions

Get my permissions Parameters:
ParameterTypeRequiredDefaultDescription
projectKeystringNoThe key of project. Ignored if projectId is provided.
projectIdstringNoThe ID of project.
issueKeystringNoThe key of the issue. Ignored if issueId is provided.
issueIdstringNoThe ID of the issue.
permissionsstringNoA list of permission keys. (Required) This parameter accepts a comma-separated list. To get the list of available permissions, use Get all permissions.
projectUuidstringNoprojectUuid
projectConfigurationUuidstringNoprojectConfigurationUuid
commentIdstringNoThe ID of the comment.

jira_users_get_user

Get user Parameters:
ParameterTypeRequiredDefaultDescription
accountIdstringNoThe account ID of the user, which uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5. Required.
usernamestringNoThis parameter is no longer available. See the deprecation notice for details.
keystringNoThis parameter is no longer available. See the deprecation notice for details.
expandstringNoUse expand to include additional information about users in the response. This parameter accepts a comma-separated list. Expand options include: * groups includes all groups and nested groups to which the user belongs. * applicationRoles includes details of all the applications to which the user has access.