Jira Service Management Cloud
Raises customer requests, reads them and their status, adds public or internal comments and closes requests in one Jira Service Management Cloud service desk. It is separate from Jira issue support, and it is a request connector for one desk, not two-way synchronisation.
| Category | Ticketing |
| Authentication | An Atlassian OAuth 2.0 (3LO) app, with a refresh token |
| Reaches | https://api.atlassian.com and Atlassian’s sign-in service |
| Needs an agent | No |
| Demo mode | No |
Availability
Section titled “Availability”Limited availability. We set this integration up with your team, starting with a pilot at your school, and check it with the provider before you rely on it.
Capabilities
Section titled “Capabilities”ticket.get, ticket.syncStatus, ticket.create, ticket.comment,
ticket.close
- Raise a request of the configured request type, in the configured desk. Plugboard reads the request type’s fields first: a type that requires anything beyond summary and description is refused, so choose one with those two only.
- Read a request and its status. Every request read must belong to the configured desk and project.
- Comment, public or internal. Jira must confirm the visibility and text that were sent.
- Close a request through one customer transition you name, by ID and name, with the status it leads to. Plugboard checks the transition is offered on the request, sends it, then reads the request again to confirm the closed status.
No approvals, attachments, other workflow transitions or search.
Getting the credentials
Section titled “Getting the credentials”- In Atlassian’s developer console, make an OAuth 2.0 (3LO) app with the
scopes
read:servicedesk-requestandoffline_access, pluswrite:servicedesk-requestwhen Plugboard should raise, comment on and close requests. - Have an agent on the desk consent to the app, and keep the refresh token from that consent.
- Note the site’s cloud ID, the service desk ID, its project key, the request type ID and, for closing, the customer transition’s ID, its exact name and the status it leads to.
The token carries only the scopes the consenting agent granted the app, which is why Plugboard uses an app rather than an API token: an API token carries that person’s full Jira rights.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Settings, Connectors, then Jira Service Management Cloud under Add a service, and Continue to setup.
Settings
Section titled “Settings”| Field | Value |
|---|---|
cloudId | The site’s cloud ID |
siteUrl | https://<site>.atlassian.net |
serviceDeskId | The service desk’s ID |
projectKey | The desk’s project key, for example IT |
requestTypeId | The request type Plugboard raises |
clientId | The OAuth app’s client ID |
allowWrites | Off by default. Turn it on only when Plugboard should raise, comment on and close requests |
closeTransitionId, closeTransitionName, closedStatusName | The closing transition. Set all three or none |
Credentials
Section titled “Credentials”| Field | Value |
|---|---|
clientSecret | The OAuth app’s secret |
refreshToken | The refresh token from the agent’s consent |
The connection test checks that the desk ID and project key belong together. It does not prove the request type’s fields or that writes are allowed: raise, comment on and close a test request during the pilot.
The refresh token
Section titled “The refresh token”Plugboard renews its own access. Atlassian answers every renewal with a new refresh token, and Plugboard stores it in the connection’s sealed credentials. A refresh token left unused for 90 days lapses, and a refused renewal reports a sign-in failure asking for the app to be authorised again.
How it behaves
Section titled “How it behaves”- Every call goes to Atlassian’s API host. Redirects are refused, and Jira’s own error text is never shown.
- Writes are never retried automatically. A write Jira does not confirm says to check Jira before trying again.
See connector configuration for shared setup concepts and the capability reference for the full limits.