Dousen + Jira Cloud

By Luca Vitiello · Updated 6 October 2026

Dousen connects to Jira Cloud in two ways. DousenDesktop reads your assigned issues with your own email and API token and shows them as the My tasks list. DousenCore uses a project-level connection to move the issue to a new status when you submit the task’s Perforce changelist.

How does Dousen list my Jira tasks?

You enter your Jira Cloud base URL, email and an Atlassian API token in Settings → Jira. DousenDesktop calls Jira directly from your machine with those credentials, so you see the issues you can see in Jira. The tab lists issues with this JQL:

assignee=currentUser() AND statusCategory != Done

Select a task to see its description as Jira renders it. The detail pane has these controls.

ButtonAction
Open in JiraOpens the issue in your browser.
Open changelistOpens a Perforce changelist for the issue.
Submit changesSubmits the linked changelist.
Restore shelved changesUnshelves the last shelved changelist for the task (preview).
The My tasks tab in DousenDesktop. The task list is on the left, with search and status filters above it. The details pane on the right shows the selected task's status, project, changelist, and description.
The My tasks tab. The screenshot uses a sample project.

Click Open changelist on a task. Dousen creates a Perforce changelist whose description starts with the issue key, such as DOU-142, and records it in DousenCore under that key. While the task stays selected, every connected DCC addon receives the task and changelist, and your exports carry them. The key stays in the submitted changelist description, so it remains in the depot history. See Dousen + Perforce for the changelist workflow.

Can Dousen move the issue when I submit?

Yes. A project admin adds the project’s Jira connection in the web portal (Jira Configuration in Project settings: base URL, project key, email and API token). The admin then names the transition in the Jira transition on CL submit pipeline setting:

jira:
  on_submit_transition: "In Review"

After a successful submit, DousenCore lists the issue’s transitions, picks the one whose name matches the setting (ignoring case) and runs it. Use the name of the workflow transition, which can differ from the status it leads to. If no transition matches, the submit still succeeds and the issue stays where it is. Saving or publishing an asset never changes the issue. If the project uses a separate source repository, the issue moves after the last non-empty changelist is submitted.

What isn’t supported?

If Jira is slow or unreachable, DousenDesktop keeps showing the last known tasks. If Jira rejects your credentials, polling stops until you save valid ones.

DousenCore also accepts signed Jira webhook events at POST /webhooks/jira, but the endpoint doesn’t change any task or changelist state.

Dousen is free during the studio beta, with access by request, and free forever for teams of up to 5 users. Request early access.