Common issues
Quick fixes for the problems people hit most often.
The Exportelier action is not visible
- Confirm the app is installed (a site admin can check Apps → Manage apps).
- Reload the issue view.
- Check that your role allows exporting — see Permissions & roles.
Permission errors
Exports run as you. If an issue or field is missing, confirm you can browse it in Jira directly.
Missing or oddly formatted fields
Unknown field types render via a safe fallback — see Field rendering problems.
A report says a data source is not available to me
The report uses a Jira Saved Filter that your account cannot see, so the export stops and names it rather than returning a report with a missing section.
Jira answers the same way for a filter that was deleted and for one that simply is not shared with you, so Exportelier does not guess between them. Ask a site admin to either share that Saved Filter with you in Jira, or point the report's data source at one you can see. Exportelier deliberately provides no way around Jira's own sharing — not even for site admins.
A report is missing issues I expected
Check the export's manifest, which states what each data source contributed. Two ordinary causes:
- A limit truncated it. A source reads at most 500 issues and a whole report at most 2 000 — the document says so when it happens. See the limits reference.
- Your Jira permissions differ from those of the person who built the report. Reports read Jira as you, so this is expected rather than a fault.
A dashboard gadget says "Needs repair"
Exportelier recognized the gadget but Jira did not hand over one of its settings — which Saved Filter it uses, or which field it groups by. Atlassian does not guarantee that a built-in gadget's preferences are readable through a public API, so this is a normal outcome, not a fault.
Pick the missing setting yourself in the repair step, or leave that gadget out of the report. Exportelier will not guess, and it will not let you create the report while anything is still unrepaired.
A dashboard gadget says "Unsupported" or "Available after R4"
Unsupported means the gadget is not one Exportelier can rebuild — usually a third-party gadget. Available after R4 means Exportelier recognized it but does not yet ship a matching component; Created vs. Resolved and Sprint Burndown are both in this group.
Neither is dropped silently. Both are listed by name in the review step, both require your explicit acknowledgement before the report can be created, and both stay named in the finished document's completeness notice.
A dashboard gadget says "Error"
Jira refused to let Exportelier read the gadget, or what came back was contradictory. This blocks the import — fix the access or the gadget's configuration in Jira, then import again.
An imported report will not export
Its completeness notice no longer matches what was imported — usually because the notice was deleted from the template, or the template was rolled back to a version that predates the import.
This is deliberate. A report that names a dashboard while silently omitting part of it is worse than no report, so Exportelier blocks the export instead. Restore an earlier template version, or re-import the dashboard. If you want a report without a managed notice, duplicate it — a duplicate has no import behind it.
"Import from Jira dashboard" is greyed out
Jira's gadget-listing endpoint no longer returns what Exportelier expects. Atlassian marks that endpoint Experimental, so it can change without notice, and Exportelier disables the import rather than acting on a response it may have misread.
Existing reports, templates and exports keep working. Check for an Exportelier update; if there is none, get in touch.
Exports are slow
Large result sets run as background jobs — see Large exports & background jobs.
A checklist-style graphic of the first things to verify.
See Getting help for how to report an issue and what details to include.