Skip to main content

Release notes

This documentation describes V1.2, released on 7 September 2026. Earlier releases are summarized below; separate documentation snapshots have not been published.

V1.2 — Category reports and the report builder (current)​

  • Legacy Code Mode: existing code templates remain readable for copying their source, but cannot render or export. Rebuild them in the visual designer. New code templates and code-template imports are disabled.

  • A reusable Category chart component with Pie, Donut, and Horizontal bar presentations, sourced from the current exported issue set.

  • Visible None, Other, truncation, and unsupported-value semantics, including assignment-based percentages for multi-value fields.

  • Truthful PDF vector, Word SVG/PNG-plus-table, and Markdown table projections.

  • Dashboard Report Standard, a bundled three-chart template for Search, Board, Sprint, Release, and Backlog exports. Despite the name it summarizes the exported issue set; importing an actual Jira dashboard is separate, below.

  • The report builder: a report combines one template with up to eight named Jira Saved Filter data sources, and components bind to a source by name. Exportelier stores a filter's id — never its JQL and never a snapshot — so a report always reflects the filter's current contents.

  • Three further report components: KPI card, Issue table, and two-dimensional matrix, complete in PDF, Word and Markdown.

  • A reusable Time series component for Created, Resolved and scalar custom Date/Date-Time events, with explicit local-calendar ranges, Jira-user time zones and Monday/Sunday week starts. PDF is vector, Word carries a chart plus complete table, and Markdown carries the exact linearised table.

  • Created vs. Resolved is a preset of that ordinary Time series component and is also supported by dashboard import. Saved Filter charts count dates only for issues matching the filter now; they do not reconstruct historical filter membership and can therefore differ from Jira's gadget.

  • Report exports run in the background, in PDF, Word or Markdown, with a per-source preflight, honest phase progress, cancel, and a finished-document manifest naming what each source contributed.

  • Every report read runs as the exporting user, so two people can legitimately get different documents. A Saved Filter that is not available to you blocks the export by name rather than quietly shrinking the report.

  • Dashboard import: build a report from an existing Jira dashboard. Exportelier reads the dashboard's configuration through Atlassian's documented API and rebuilds it from its own components — a semantic import, not a screenshot. Filter Results, Pie Chart, Work Item Statistics, Two Dimensional Filter Statistics and Created vs. Resolved are supported; Sprint Burndown is not yet available; unknown and third-party gadgets are named and can only be excluded after an explicit acknowledgement. Where Atlassian does not expose a gadget's settings, you choose the filter or field yourself rather than Exportelier guessing. Every imported report carries a completeness notice naming what was left out, and cannot export if that notice is removed. Filter data stays live; layout and configuration update only on an explicit re-import.

V1.1 — DOCX & Word Template Mode​

  • Editable Word (DOCX) output on every export context.
  • Word Template Mode: fill your own branded .docx with Jira data.
  • Scheduled exports.

V1.0 — Public launch​

  • All six export contexts.
  • The visual template designer.
  • Branding, digital signatures and the audit log.
  • The Jira Automation action and the Exportelier Automation app.

Current and planned​

  • Available now: company-wide and project-scoped templates in Free and Standard.
  • Later roadmap: role-based access, AI-assisted summaries, conditional sections, and the path to Cloud Fortified certification. These ideas have no committed release or edition.
Roadmap

Plans are stated honestly and may shift. The website roadmap has the latest.