Component library
The designer gives you 34 drag-and-drop components. You assemble a template by dropping components onto the canvas and binding them to Jira data. This page is a reference to the component groups.
The designer's component palette with the component groups expanded.
Layout
Structural building blocks that arrange everything else: sections, columns, spacers, page headers and footers, and page breaks. See Layout & page setup.
Fields
Bind a component to any standard or custom Jira field — summary, status, assignee, dates, numbers, select lists, and more. Unknown field types fall back safely. See Binding components to Jira data.
Status, Priority and Issue type can additionally render as a badge rather than plain text, matching how the same status looks inside a sub-task table. Status takes its colour from the Jira status category, so a renamed or non-English status still colours correctly; priority and issue type get their Jira icon and a neutral chip. The option is greyed out for every other field, including your own single-select custom fields — there is no category behind those values to colour by.
Repeaters
Repeat a block of components once per issue (in bulk/board/sprint exports) or per item in a list, with optional grouping. See Repeaters & grouping.
Lists and tables
Ready-made components for issue content:
- Comment lists — optionally with author avatars (off by default; read only from your own Jira site, initials otherwise)
- Worklog tables (with a Tempo mirror mode — see Tempo)
- Change history
- SLA & approval lists (useful for Jira Service Management)
Category charts
A Category chart is a normal, reusable component. Drop it anywhere a component is allowed and bind it to a groupable Jira field. In a normal export template its source is always the current exported issue set; adding a chart performs no extra Jira search. Inside a report it can instead read one of the report's named data sources.
Choose a Pie, Donut, or Horizontal bar presentation. Empty values appear as None. When the category limit is exceeded, extra categories are either combined into Other or truncated. Truncation and unsupported values always produce a visible note instead of silently omitting data.
For multi-value fields such as Labels, percentages use the total number of category assignments, not the number of issues. One issue assigned to three labels contributes three assignments.
The same component has truthful format-specific projections:
- PDF: a vector chart with text labels and values.
- Word (DOCX): embedded SVG with a PNG fallback, followed by a category table.
- Markdown: a category table; horizontal bars also use text bars. Pie and Donut are not represented by a fake image.
Category names and values remain available as text, so colour is never the only information.
Time series
A Time series is another normal issue-set component. Use one to four series, each counting Created, Resolved or a scalar Date/Date-Time custom field. The Created vs resolved palette item is only a preset of the same component: it starts with Created and Resolved series, and every setting remains editable.
Resolved means Jira's resolutiondate only. A Done status without a resolution
date is not counted as a resolution event.
Choose Line, Area or Grouped bars; day, week or month buckets; and an inclusive relative or fixed range. Relative ranges end on the exporting user's local date at generation time. Month means a local calendar month, not 30 days, and week start is always the explicit Monday/Sunday setting. If the user's Jira time zone cannot be used, the export falls back to UTC and says so visibly.
A Saved Filter supplies the issues it matches now. The chart can use historical dates on those issues, but it does not reconstruct earlier filter membership. See Report components before comparing an imported Created-vs-Resolved chart with Jira's gadget.
The format badges reflect the real output: PDF is vector, Word embeds SVG with a PNG fallback and includes the full table, and Markdown is a linearised data table. See the limits reference.
Summary components
Three further components summarise a whole issue set rather than one issue:
- KPI card — one headline number: issue count, completed count, completion percent, or the sum/average of a numeric field
- Issue table — one row per issue with the columns you choose, up to 200 rows
- Two-dimensional matrix — a cross-tab counting issues by two fields, up to 12 buckets per axis, with optional totals
Like the category chart, each reads the current exported issue set in a normal template and a named data source inside a report. See Report components for the per-format detail.
Change report
Three components render what changed between a reference point and now, instead of the current state:
- Change summary — counters, the reference point, and caveats such as a first run or a gap in the change history
- Delta issue list — the Added or the No longer in result list
- Change table — one row per changed field; repeated changes to one field collapse into a single row carrying a step count
"No longer in result" never means deleted: an issue can leave a filter for many harmless reasons, and the exported document always says so.
Available on Standard for JQL, board, sprint, release and backlog exports, and especially useful in scheduled exports as a weekly "what moved" report.
Signature blocks
Drop a signature block for sign-off documents. Combine with digital signatures for tamper-evident PDFs.
Every component appears, pre-arranged, in the bundled templates. Duplicating a bundled template is the fastest way to learn what each component does — see Managing templates.