Jira tasks

Updated July 2026

Dousen doesn't store your tasks. Jira Cloud is the single source of truth: the tasks table was dropped from DousenCore's database once Jira took over, and DousenDesktop reads issues straight from Jira on every fetch rather than caching a copy server-side. Two independent Jira connections exist side by side, and this page covers both:

• Your personal connection — your own email + API token, entered in Settings → Jira — used only to read issues into the My Tasks panel. It never touches DousenCore.
• A project-level connection — base URL, project key, and email, configured by an admin on the project's page in the web portal — used only by DousenCore itself, server-side, to push the issue forward when a changelist is submitted. See Transitioning the issue on submit.

Connecting your Jira account

Open Settings → Jira and fill in three fields:

Test Connection sends GET /rest/api/3/myself with your two credentials over HTTP Basic auth and reports connected or failed based on whether Jira answers with 200 — nothing else is checked or saved by the test itself.

Your token is stored locally, separate from your Dousen login session, and is never sent to the Dousen server — every Jira request goes straight from your machine to Jira Cloud over Basic auth. On Windows it's kept in the OS Credential Store. Elsewhere it's XOR-obfuscated with a random per-install key (itself written to a sibling file with owner-only permissions) — enough to stop a casual look at the config file, not real encryption; an OS-keychain integration for Linux/macOS (libsecret / Keychain) is on the backlog.

The My Tasks panel

My Tasks shows the issues assigned to you that aren't yet Done. It runs one fixed JQL query:

TEXTassignee=currentUser() AND statusCategory != Done

Results page 50 issues at a time. A Load more tasks button appears under the list whenever Jira's response says more remain (startAt + returned < total), and fetches the next page without disturbing what's already shown. The whole list is polled every 30 seconds by default — configurable under Settings → Connection → Task poll interval, anywhere from 5 seconds to an hour — so newly assigned work shows up on its own.

Selecting a task loads its detail on the right: status badge, Jira key, project, task id, a linked-changelist indicator, a shelved-changelist indicator (see Shelving), and the description rendered as real HTML — headings, lists, and inline images — from Jira's renderedFields.description, not a plain-text fallback. Images referenced in the description (Jira's /secure/attachment/... URLs) are fetched with the same Basic-auth credentials, cached in memory for the session, and scaled down to fit the pane if they're wider than it.

Staying usable through outages

The panel is built to keep showing something useful when Jira is slow, unreachable, or rejects your credentials:

• Cold start. On launch, the last successfully-fetched task list loads from a local on-disk cache immediately — before the first live fetch even completes — so the list isn't empty while Jira is loading or unreachable.
• Network outage. If a poll gets no HTTP response at all (DNS failure, timeout, connection refused), Dousen backs the poll interval off in steps — your configured interval, then 60 seconds, then 5 minutes, capped — and shows one persistent "Offline" banner instead of an error toast on every failed tick. The first successful fetch afterward restores your configured interval and clears the banner.
• Bad credentials. A 401/403 from Jira is treated differently from a network error: retrying with the same token can never succeed, so polling stops outright and a banner tells you to fix your email or token in Settings. It resumes automatically the moment you save valid credentials there.

Details in Troubleshooting.

Linking a task to a Perforce changelist

Selecting a task and clicking Open CL opens a Perforce changelist and links it to that Jira issue key (for example DOU-142) inside DousenCore — the changelist row is keyed by the plain issue-key string, not a foreign key into any task table (there is none). From that point, exports published while the task stays selected carry both the task and the changelist, via the task.context bridge event every DCC addon subscribes to — see DCC addons.

1. Pick your task in the My Tasks panel.
2. Click Open CL.
3. Work and publish as normal — the DCC addons pick up the active task and changelist automatically.
4. Click Submit when the work is ready. See Perforce for exactly what happens to the changelist.

Transitioning the issue on submit

Submitting the linked changelist can automatically move the Jira issue forward — DousenDesktop itself never calls Jira for this; DousenCore does, server-side, using its own project-level Jira credentials. Two independent pieces of admin setup are required:

1. A project-level Jira connection — separate from any artist's personal Settings → Jira credentials — configured on the project's page in the web portal's Jira Configuration section: Base URL, Project key, and Email.
2. The jira.on_submit_transition pipeline setting, naming the transition to run:

YAMLjira:
  on_submit_transition: "In Review"

On a successful submit, DousenCore looks up the target transition by name (GET /rest/api/3/issue/{key}/transitions, matched case-insensitively) and fires it (POST /rest/api/3/issue/{key}/transitions) using the project's Jira credentials — not yours. A name that doesn't match any available transition, or any other failure, is logged server-side and the submit still succeeds; it just doesn't move the issue.

The desktop app only supplies this by including your active project in the submit request — pick one from the project selector before submitting, or the server has no project to resolve the setting from and silently skips the transition.

Inbound Jira webhook

DousenCore also accepts webhook events from Jira at POST /webhooks/jira, verified with an HMAC-SHA256 signature over the raw body: