Aller au contenu

// integration

Atlassian Jira

Applies to

Product: Cloud · Server · Audience: Administrator

The Atlassian Jira connector lets the basebox assistant search, read, create, edit and assign issues in Jira and move them to another status, including Jira Service Management requests and queues. It works with Atlassian Cloud and with Jira Server / Data Center. Confluence has its own connector, Atlassian Confluence.

What does the connector do?

This and the following sections are generated from the information the connector's image carries. What applies to every connector is described under What applies to every connector.

In the catalog it describes itself as:

Search, read and edit Jira issues.

It gives the assistant these instructions:

Jira, seen with the user's own account: absent results can mean 'not permitted' as well as 'not there'. Find issues with jira_search, then read one with jira_get_issue. To change an issue's status, get its transitions first. Ask before deleting anything or changing fields the user did not mention.

Settings

The administrator fills in these fields in the connector's settings. They apply to the whole organisation.

Field Required Meaning
Jira URL no On Atlassian Cloud the site address; on Server/Data Center the Jira web root. Example: https://acme.atlassian.net
Help links for signing in no One link per sign-in method, e.g. a page on your intranet explaining how to create an API token.

Sign-in

The administrator decides how the connector signs in: with Personal sign-in each person signs in with their own account and sees only what they may. With Company account everyone uses one account the administrator enters.

Personal sign-in

  • Email and API token (Atlassian Cloud) – asks for a username and password. Create an API token at id.atlassian.com → Security → API tokens.
  • Personal access token (Server / Data Center) – asks for a token. Create one in Jira under your profile → Personal Access Tokens.

Company account

  • Service account's email and API token (Atlassian Cloud) – asks for a username and password. A dedicated Atlassian account with access to what every user may see.
  • Service account's personal access token (Server / Data Center) – asks for a token.

A company account gives everyone the same rights

Every basebox user reaches the system with the rights of this one account. Results are not trimmed to what each person may see.

The connector adds:

Every basebox user sees the issues this one account can see, and every comment or change they make is recorded under its name.

Tools

The assistant can call 36 tools.

Tool Effect Description
check_connection reads Checks that the user's Jira credential is accepted and returns the signed-in user.
jira_add_watcher writes Makes a user watch a Jira issue and returns the issue's watchers.
jira_assign_issue writes Assigns a Jira issue to a user, or unassigns it, through Jira's dedicated assignment endpoint, which works where setting the assignee field is ignored. Returns the issue's new assignee.
jira_batch_create_issues writes Creates up to 50 Jira issues in one request and returns the keys of those created and the reasons for any refused. Can instead only check them and return the request it would send.
jira_batch_create_versions writes Creates up to 50 fix versions in a Jira project and reports, for each, the version created or why Jira refused it.
jira_batch_get_changelogs reads Reads the change history (who changed which field when) of several Jira issues at once. Atlassian Cloud only.
jira_create_customer_request writes Creates a Jira Service Management customer request of a request type and returns it with its issue key. Required fields left empty are refused before anything is created. If the request cannot be raised on behalf of the given customer, it is raised by the user instead unless strict_on_behalf is set; that, and files that could not be attached, are reported in warnings.
jira_create_issue writes Creates a Jira issue in a project and returns its key. Fields a project requires beyond summary and description go in additional_fields; if one is missing, the error names it.
jira_create_version writes Creates a fix version in a Jira project and returns it with its id.
jira_delete_issue modifies or deletes Deletes a Jira issue permanently. Jira refuses while the issue has subtasks.
jira_get_all_projects reads Lists the Jira projects the user can see, with their key, name and description.
jira_get_create_fields reads Lists the fields an issue of one type takes when created in a Jira project: which are required, their schema and the values select fields allow.
jira_get_field_options reads Lists the values a Jira select, radio, checkbox or cascading select custom field allows. Atlassian Cloud reads them from the field's context; Jira Server/Data Center needs the project and issue type whose create screen has the field.
jira_get_issue reads Reads one Jira issue by its key, with its description and newest comments in Jira wiki markup, its status, people, dates, links and subtasks. Can inline its transitions, changelog, watchers, remote links and worklogs.
jira_get_issue_watchers reads Lists who watches a Jira issue and whether the signed-in user does.
jira_get_project_components reads Lists a Jira project's components with their ids and leads.
jira_get_project_fields reads Lists the fields issues of a Jira project can have, each once with the issue types it appears on and whether it is required there.
jira_get_project_issue_types reads Lists the issue types that can be created in a Jira project, with their ids.
jira_get_project_issues reads Lists one page of a Jira project's issues, newest first, with their key, summary, status and other basic fields.
jira_get_project_versions reads Lists a Jira project's fix versions, released and unreleased, with their ids and dates.
jira_get_queue_issues reads Lists one page of the issues in a Jira Service Management queue, with their key and the fields the queue shows.
jira_get_request_type_fields reads Lists the fields a Jira Service Management request type asks for, with each field's id, name, whether it is required and its valid values, and whether the user can raise requests on behalf of customers.
jira_get_request_types reads Lists one page of the request types customers can raise at a Jira Service Management service desk, with each type's id, name and description.
jira_get_service_desk_for_project reads Finds the Jira Service Management service desk of a project, with its id, name and project.
jira_get_service_desk_queues reads Lists one page of the queues of a Jira Service Management service desk, with each queue's id, name, JQL and issue count.
jira_get_transitions reads Lists the workflow transitions a Jira issue can take from its current status, with each transition's id and target status.
jira_get_user_profile reads Reads the profile of one Jira user, found by account id, username, email address or display name, or of the signed-in user.
jira_move_issue modifies or deletes Moves a Jira issue to another project, keeping its issue type; it usually receives a new key there, which the result shows. Waits up to 30 seconds for Jira to finish. Atlassian Cloud only.
jira_remove_watcher modifies or deletes Stops a user watching a Jira issue and returns the remaining watchers.
jira_search reads Searches Jira issues with a JQL query and returns one page of them with their key, summary, status and other basic fields, optionally restricted to some projects. The response tells how to fetch the next page: a nextPageToken on Atlassian Cloud, startAt and total on Jira Server/Data Center.
jira_search_assignable_users reads Finds the users who can be assigned issues of a Jira project or a single issue, matching part of their name, username or email address. Returns account ids on Atlassian Cloud and usernames on Jira Server/Data Center, as assignee and watcher arguments take them.
jira_search_fields reads Finds Jira field definitions by part of their name or id, to learn the id of a custom field such as Story Points (e.g. customfield_10016) and its type.
jira_search_projects reads Finds Jira projects whose name or key matches a text, without listing every project.
jira_transition_issue writes Moves a Jira issue to another status by a workflow transition id, optionally setting fields the transition requires and adding a comment, and returns the issue's new status. The ids an issue can take depend on its current status.
jira_update_issue modifies or deletes Changes fields of a Jira issue, such as its summary, description, priority, assignee or components, and returns the issue as stored. The status cannot be set this way; it changes through a workflow transition.
jira_update_version modifies or deletes Changes a Jira fix version's name, description, dates, or its archived or released flag; attributes not given stay as they are. Returns the version as stored.

Generated from mcp-atlassian-jira:v0.2.1.