Jira tasks
Dousen doesn't store your tasks — Jira is the single source of truth. DousenDesktop reads your issues straight from Jira Cloud and links the work you publish to the right issue, so your task board stays accurate without manual updates.
How your tasks are fetched
DousenDesktop fetches issues directly from Jira Cloud using your own credentials — your account email and a personal API token. The token is stored locally on your machine.
Your Jira API token is never sent to the Dousen server. It stays on your computer and is used only to talk to Jira directly.
Connecting Jira
Open Settings → Jira and fill in:
- Base URL — your Jira Cloud site (for example
https://yourstudio.atlassian.net). - Account email — the email you sign in to Jira with.
- API token — a personal token created in your Atlassian account.
Use the Test Connection button to confirm the three values work before saving — it asks Jira who you are and shows a green check or a failure on the spot.
Admins can hand out the base URL in a config bundle, so you may only need to enter your email and token. The first-run onboarding asks for the same three values, so most artists never open this tab at all.
The My Tasks panel
My Tasks shows the issues assigned to you that aren't yet Done. Under the hood it runs the query:
JQLassignee = currentUser() AND statusCategory != Done
It's a split view: the task list is on the left, and the selected issue renders on the right — status badge, Jira key, project, linked changelist, and the full description as rich HTML including any images. The list loads 50 issues at a time with a Load more tasks button, and refreshes itself every 30 seconds (configurable under Settings → Connection) so newly assigned work shows up on its own.
The detail pane's footer buttons act on the selected issue: Open in Jira jumps to it in the browser, and Open CL / Submit / Unshelve drive the linked Perforce changelist — see Perforce.
If Jira can't be reached, the panel shows an "Offline" banner and backs off its polling until the connection returns; if your credentials are rejected it pauses and tells you to fix them in Settings. Details in Troubleshooting.
Linking a task to a Perforce changelist
Selecting a task and opening a changelist links that changelist to the Jira issue key (for example DOU-142). The changelist is created through the desktop app and tracked by Dousen. From that point on, everything you publish while the task is active is tagged to it.
- Pick your task in the My Tasks panel.
- Open a changelist for it from the desktop app.
- Work and publish as normal — exports are automatically associated with both the task and the changelist.
Transitioning the issue on submit
When you submit the linked changelist, Dousen can automatically move the Jira issue forward. This happens if your project admin set a transition name under jira.on_submit_transition in the project's pipeline settings.
YAMLjira:
on_submit_transition: "In Review"
The transition runs server-side, so the status updates even after you've closed the desktop app.
Two-way sync
Status changes also flow back the other way. Dousen receives updates from Jira through a webhook at /webhooks/jira, so when an issue's status changes in Jira, Dousen stays in step.