Jira Data Center
Read and update Jira Data Center issues from a workbench
The Jira Data Center tool lets a workbench agent work with issues on a self-hosted Jira Data Center instance. Configure it with a dedicated account and personal access token, then attach it to the workbenches that should use it.
This guide uses the Plural Console UI. For the complete list of integrations and general tool behavior, see Workbench tools.
Prerequisites
Before you begin, make sure you have:
- A self-hosted Jira Data Center instance accessible from your Plural deployment.
- Permission in Plural Console to create a configured tool and edit the target workbench.
- A dedicated Jira account for the integration, with only the project permissions the workbench needs.
- A personal access token for that account. See Create a personal access token below.
- An existing workbench, or permission to create one. See Setting up a workbench.
Capabilities
The agent can call these operations on the configured Jira Data Center instance:
jira_list_issues— Search Jira issues with JQL (Jira Query Language). Returns paginated results with offset-based pagination. Supports field selection to limit the response size.jira_get_issue— Get a single Jira issue by key or ID. Supports field selection and expansion of related data such as changelog or rendered fields.jira_save_issue— Create a new issue or update an existing one. Requires project key, issue type, and summary for creation. Updates apply only the fields provided in the request.jira_list_comments— List comments on an issue. Returns paginated results with offset-based pagination.jira_save_comment— Create a new comment or update an existing one on an issue. Supports visibility restrictions (role or group).jira_list_transitions— List the workflow transitions available for an issue based on its current status and the account's permissions.jira_transition_issue— Transition an issue through its workflow. Can optionally set fields or add updates as part of the transition.
All operations use the Jira REST API v2 (/rest/api/2) with Bearer authentication (personal access token). The implementation is shared with the Jira Cloud tool, but pagination uses integer offsets (startAt) instead of opaque tokens.