Jira
Import issues from your Jira Cloud projects into Decuga
Overview
The Jira connector imports issues from your Jira Cloud workspace into Decuga as tasks. It authenticates using HTTP Basic Auth with your Atlassian email address and a personal API token — no OAuth partner application required.
You can optionally limit imports to a specific project and filter by issue status. The connector skips issues already imported (de-duplication by Jira issue key).
Setup
Generate an Atlassian API token
Log in to your Atlassian account and navigate to:
https://id.atlassian.com/manage-profile/security/api-tokensClick Create API token, give it a descriptive label (e.g. Decuga import), then click Create.
Find your Jira domain
Your Jira domain is the hostname you use to access Jira Cloud, for example:
your-company.atlassian.netDo not include https:// — Decuga adds this automatically. If you paste a full URL it will be stripped.
Find your project key (optional)
A project key identifies a Jira project (e.g. PROJ, ENG). You can see it in the URL when browsing issues:
https://yourco.atlassian.net/jira/software/projects/PROJ/boardsLeave blank to import all projects your account has access to.
Connect Jira in Decuga
In your Decuga project, go to Settings → Integrations and click Connect on the Jira card. Fill in the form:
| Field | Description |
|---|---|
| Jira Domain | your-company.atlassian.net |
| Atlassian Account Email | The email you use to log in to Jira |
| API Token | The token generated in step 1 |
| Project Key (optional) | e.g. PROJ — leave blank for all projects |
| Status filter (optional) | All, To Do, In Progress, or Done |
Click Connect to save the integration.
Run your first import
Once connected, click Import now on the Jira card. Imports run asynchronously — expand Import history to monitor progress. Re-running an import skips issues already present (matched by Jira issue key).
Field mapping
Jira issue fields are mapped to Decuga task fields as follows:
| Jira field | Decuga field |
|---|---|
| summary | Title |
| description (Atlassian Doc Format) | Description (plain text extracted) |
| status.statusCategory | Status — To Do / In Progress / Done |
| priority.name | Priority — Low / Medium / High |
| duedate | Due date |
| key (e.g. PROJ-42) | External ID (stored in custom fields) |
Troubleshooting
Authentication failed (HTTP 401)
Double-check your email and API token. Make sure you are using the token value, not your Atlassian account password.
No issues imported
Verify the Project Key is correct and that your Atlassian account has access to that project. Try clearing the project key to import all accessible projects.
Import says "0 fetched"
The JQL query returned no results. Try changing the Status filter to "All" or leave the Project Key blank.
Description appears blank
Jira Cloud uses Atlassian Document Format (ADF) for descriptions. The connector extracts plain text. Complex documents with only media or tables may produce no text output.