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, epics and sub-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 Integrations → Connections 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) |
Epics and sub-tasks
On Pro and above, the connector reads the epic structure of your Jira projects and recreates it in Decuga (see the Epics documentation).
| In Jira | In Decuga |
|---|---|
| Epic issue (type Epic) | Epic - title, description and due date are copied; the status category sets the epic status (To Do → Planned, In Progress → In progress, Done → Done) |
| Story / task / bug whose parent is an epic | Task in that epic |
| Story with an Epic Link (older company-managed projects) | Task in that epic - the Epic Link field is found automatically |
| Sub-task | Sub-task of its parent task, in the parent's sprint and epic |
- Epics are imported first, so every issue can point at its epic. They ignore the status filter: a task may belong to an epic that is already done.
- Re-running an import updates the epics already imported (title, description, status and target date follow Jira) and keeps the colour, owner, start date and roadmap link you set in Decuga. It never takes a task out of an epic you chose in Decuga.
- A sub-task whose parent is not part of the import (filtered out, or in another Jira project) is imported as an ordinary task.
- On Free and Starter no epics are created: Jira epics are imported as ordinary tasks, as before. Upgrade to Pro to import them as epics.
Jira Service Management projects
Enter the key of a Jira Service Management project and the whole project is imported as Service Desk tickets instead of tasks. Other project types keep coming in as tasks. Nothing is sent to anyone while this runs: customers are not emailed and agents are not notified.
| In Jira | In Decuga |
|---|---|
| Summary, description | Ticket title and description. The Jira key and link are kept on the ticket. |
| Status category | To Do → Open, In Progress → In Progress, Done → Resolved (or Closed when the Jira status is named Closed, Cancelled or Declined) |
| Priority | Highest/Critical/Blocker → Urgent, High/Major → High, Medium → Medium, Low/Lowest/Minor → Low |
| Created, resolved | The original dates are kept |
| Reporter | The ticket reporter, matched by email to an existing reporter or created. If Jira does not show the customer’s email, the name is kept on the ticket instead. |
| Customer organization | The Decuga company with the same name, when there is one. Companies are never created by the import. |
| Public comments | Replies. The customer’s own comments are shown as theirs. |
| Internal comments | Internal notes: only your team sees them |
| Attachments | Ticket attachments (25 MB limit each) |
- Re-running the import updates the tickets already imported (title, description, status, priority) and adds new comments. It keeps the assignee, tags and SLA you set in Decuga.
- Imported tickets have no SLA applied until someone edits them, so old tickets do not raise breach alerts.
- Tickets get Decuga ticket numbers in the project's own sequence. Assignees are not mapped.
- If Decuga cannot tell what type the Jira project is, it imports it as tasks.
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.
My Jira epics show up as tasks
Epics are imported as Decuga epics on the Pro plan and above. On Free and Starter they come in as ordinary tasks. After upgrading, re-run the import to get real epics for the epics that are still in Jira.
A story is not in its epic
The epic has to be part of the import. Make sure the Project Key covers the epic's project. Stories whose epic lives in another Jira project can only be linked if that project is imported too.
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.