Report components
Five components read a whole issue set rather than a single issue. They are ordinary designer components — you drag them onto the canvas like any other — but each one carries a data source setting.
Binding a component to data
Every one of these components asks the same question: which issues?
| Where you are | What the source selector offers |
|---|---|
| A normal export template (issue, board, sprint, release, backlog, JQL) | Current export set — the issues being exported. No extra Jira search. |
| A report | The report's named data sources. |
The two are not interchangeable. A named source only resolves inside a report; a component bound to one that no longer exists renders a visible diagnostic naming the missing source, in every format. It never silently renders empty.
When a report has more than one source, nothing is guessed. A chart bound to the wrong filter produces a document that looks correct and is not, which is worse than one that plainly fails.
Time series
Plots date events from an issue set as a line, area or grouped bar chart. A component contains between one and four series. Each series counts one of three event types:
| Event | What is counted |
|---|---|
| Created | The issue's Created timestamp. |
| Resolved | The issue's Jira resolutiondate, and nothing else. A current Done status is never treated as evidence of a resolution event. |
| Custom date | One scalar custom field whose Jira schema is Date or Date/Time. Multi-value date fields are ignored with a visible warning. |
Choose day, week or month buckets and either a relative or fixed range. Both ranges are inclusive. A relative range ends on the local calendar date of the export's explicit generation time; a fixed range includes both From and To. Empty buckets can be retained, and must be retained for a cumulative series so flat sections of the curve do not disappear.
Calendar boundaries use the exporting user's Jira time zone. If Exportelier cannot read it, or Jira returns an invalid zone, the chart falls back to UTC and prints a warning in the document. A month bucket is a local calendar month, not 30 elapsed days. Weeks start on Monday or Sunday according to the component's explicit setting; the server's locale never chooses for you.
A Saved Filter source returns the issues that match the filter now. The chart counts historical Created, Resolved or custom-date events only for those issues; it does not reconstruct which issues matched the filter in an earlier period.
For that reason, an Exportelier Created-vs-Resolved chart can differ from Jira's own Created-vs-Resolved gadget when the two are compared after a dashboard import, and that difference is not necessarily a calculation bug.
Bucket limits are enforced when the template is saved: 366 day, 104 week, or 60 month buckets. A larger configuration is refused instead of silently shortening the curve.
Category chart
Groups the issue set by one groupable field and draws the distribution as a pie, donut or horizontal bar chart.
- At most 20 categories; beyond that, the extra categories are combined into Other or truncated, depending on the component's setting.
- Empty values appear as None.
- For multi-value fields such as Labels, percentages count category assignments, not issues — one issue with three labels contributes three.
- Truncation and unsupported values always produce a visible note.
KPI card
A single headline number with a label. Choose one metric:
| Metric | What it counts |
|---|---|
| Issue count | Issues in the source. |
| Completed issue count | Issues whose status category is Done. |
| Completion percent | Completed issues as a percentage of the source. |
| Numeric field | The sum or average of a numeric field. |
Numeric aggregation accepts finite numbers only. Values that are empty or not a number are ignored and counted visibly, so a card built on a half-filled field never silently misleads you about its own basis.
Optionally, the card shows the name of the data source it read — useful when several cards sit side by side.
Issue table
One row per issue, with the columns you choose.
- Pick any standard or custom field per column, with an optional custom header and width.
- Optional sort by a field, ascending or descending.
- Up to 200 rows. When the source has more, the table shows the first rows and states how many were omitted.
- Optional row-count line ("12 of 47 rows") and optional header row.
Field values are rendered and coerced exactly as in Exportelier's other tables, so a custom field looks the same wherever it appears.
Two-dimensional matrix
A cross-tab: one field down the rows, another across the columns, counting issues in each cell.
- Both axes are capped at 12 buckets. Beyond that, the remaining values collapse into a deterministic Other bucket — the same input always produces the same table.
- Optional row totals, column totals and a grand total.
- Rendered as a real, accessible table in every format, never as an image.
How each format renders them
Exportelier compiles one template to four formats. The table below reflects what the renderers actually produce — a format is only marked complete when it carries every value, not when it merely looks similar.
| Component | Word (DOCX) | Markdown | Excel (XLSX) | |
|---|---|---|---|---|
| Time series | Vector axes, lines, areas or bars with text legend and optional values/table | Embedded SVG with deterministic PNG fallback, followed by the complete data table | Linearised table with one row per bucket and one column per series; no pseudo-line image | Data sheet: a typed bucket date plus one number column per series. No chart picture — the numbers are there to plot yourself. |
| Category chart | Vector chart with labels and values | Embedded SVG with PNG fallback, followed by a category table | Category table; horizontal bars also get text bars. Pie and donut are not faked as an image. | Data sheet with Category, Count and Percent columns |
| KPI card | Complete | Complete | Complete | One row on the shared Summary sheet, not a sheet of its own |
| Issue table | Complete | Complete | Complete | Complete — one row per issue, one column per configured column |
| Matrix | Complete | Complete | Complete | Complete — row buckets × column buckets, with totals when configured |
Category names and numbers always remain available as text, so colour is never the only carrier of information.
Markdown output escapes anything in your Jira data that would otherwise break the table structure, so issue text stays issue text.
Limits
A report may contain at most 30 data-driven components. Together with the per-source and per-table caps, this bounds what a single export costs — see the limits reference.