Status badges & progress
Make child issues and linked issues easier to scan with status badges, Jira issue-type and priority icons, strike-through for completed items, and progress bars. Available in all editions.
Existing templates keep their previous appearance. These options are written explicitly only when you add a new Subtasks, Issue links or Progress bar component.
Child and linked issues
Select a Subtasks component to configure:
- Layout — a table, or individual panels. Panels keep one shared column header and show nested child issues with indentation and connector guides; turn off Show header when the labels are not needed.
- Status style — plain text or a badge.
- Show issue type icon — uses the Jira icon where available.
- Strike through completed items — applies only when Jira reports the stable status category
Done, so a renamed or translated status such as Abgenommen still works. - Show subtask progress — adds an issue-count bar across all displayed child issues, including recursively loaded ones.
- Colour mode — colour, or a print-friendly monochrome palette.
The Issue links component offers the same badge, icon, strike-through and colour controls, plus an optional priority display.
Standalone progress bar
Drag Progress bar from the Data section of the palette. It can measure:
- Subtasks — every displayed child issue, recursively.
- Linked issues — deduplicated by issue key.
- Export set — the issues in a JQL, board, backlog, sprint or release export.
Choose Issue count or Story points as the basis. Story-point progress works with every source and uses the numeric custom field selected in the properties panel. Missing, non-numeric, zero and negative values contribute zero points, and repeated references to the same key are counted once.
Labels can show a percentage, a fraction, or both — for example 67% (2/3). An empty source shows 0% by default; enable Hide when the source is empty to remove the component instead.
Status categories and unknown data
Colours and completion derive only from Jira's status category — To Do, In Progress or Done. Exportelier never guesses from a status name. Legacy data carrying only a name renders as neutral Unknown, counts in the progress denominator, and never counts as completed.
Differences between formats
| Format | Status and icons | Progress | Completed items |
|---|---|---|---|
| Vector badges, Jira bitmap icons or a drawn fallback shape | Vector bar with optional label | Native text strike-through | |
| Word (DOCX) | Shaded, bordered badge runs; Jira icons or a generic glyph | Proportional two-cell table with optional label | Native strike run |
| Markdown | [DONE], [IN PROGRESS], [TODO] or [UNKNOWN]; issue types and priorities as text | Compact text such as 67% (2/3) | ~~strike-through~~ |
Markdown deliberately embeds no bitmap icons, colour or emoji. This keeps the output portable and preserves Compact mode's token savings.
Icon handling and limits
Icons are loaded only from Jira through Atlassian's product API. Exportelier adds no external network destination and stores no icon bytes in the saved issue bundle — the bytes exist only for the current render.
- Up to 32 distinct icons per render.
- Up to 128 KiB per icon and 2 MiB in total.
- Four concurrent icon requests and a five-second total budget.
- PNG, JPEG, GIF and BMP are accepted; other formats fall back to a drawn generic shape.
- A blocked, missing, oversized or timed-out icon never fails the export.
Accessible and print-friendly output
Status text always remains visible, so colour is never the only signal. Use Monochrome for black-and-white printing or when a template should avoid semantic colour; badge borders and text contrast stay distinct. Markdown's explicit text markers are the colour-independent equivalent.