Junban Desk comes in two editions. The Cloud edition is available now; the Marketplace edition is coming soon.
The Cloud edition is hosted, so there is nothing to install into Jira.
That’s it — the workspace opens on the project’s needs-action queue. The Cloud edition works with both classic Jira Service Management and Customer Service Management projects.
Once the Atlassian Marketplace listing is live:
There is nothing to configure. Open any Jira Service Management project and choose Junban Desk in the project sidebar, under Queues.
Both editions request the minimum OAuth scopes needed for the workspace, and every Jira API call runs as the logged-in user — so Jira’s own permission checks always apply. An agent can never see or do anything through Junban Desk that they couldn’t do in Jira directly.
| Scope | Why | Editions |
|---|---|---|
read:jira-work |
Load the queue, ticket details, and comment threads | Both |
write:jira-work |
Post replies and internal notes, transition and assign tickets | Both |
read:jira-user |
Show reporter/assignee names and the assignable-user dropdown | Both |
read:servicedesk-request |
Look up the “Time to resolution” SLA for the optional SLA column | Marketplace |
offline_access |
Refresh the session token so you stay signed in between visits | Cloud |
Marketplace edition runs on the Atlassian Forge Platform (asUser()); it makes no external network calls and
stores no data outside Atlassian — see the privacy policy.
Cloud edition is hosted outside Atlassian and connects to your Jira site over Atlassian’s REST API; its data handling differs — see app.junbandesk.com/privacy.
The Open Source Forge edition (Apache 2.0) — run your own copy on your own Forge app id; see the README. Self-hosting instructions are included.
Test without any installation or admin action: The Cloud edition runs as a hosted service at app.junbandesk.com.