Skip to main content

Template designer

Other export apps make you write XSL-FO, Velocity or Groovy. Exportelier gives you a canvas, a component palette and a live preview — you design templates like a deck, not like a build script.

What's in the box​

  • 34 drag-and-drop components — layout blocks, fields, repeaters, Category charts, comment lists, worklog tables, change history, SLA & approval lists, and signature blocks.
  • Live PDF, Word & Markdown preview — see exactly what ships while you edit, against realistic sample data, with a one-click DOCX download.
  • Version snapshots — every save is restorable in one click, and you can restore the bundled defaults at any time.
  • Layout control — portrait or landscape, A4 or Letter, with margins and page breaks.

A typical workflow​

  1. Start from a bundled template or a blank canvas.
  2. Drag components onto the page and bind them to Jira fields.
  3. Group and repeat content (for example, group a sprint report by status).
  4. Watch the live preview update against sample data.
  5. Save — a version snapshot is created automatically.
Restore anything

Because every save is a restorable snapshot, you can experiment freely. If a change doesn't work out, restore the previous version — or the bundled default — in one click.

Nine ready-made templates​

Exportelier ships with nine polished default templates so you get a useful document from the first minute, before you design anything of your own. Dashboard Report Standard provides a reusable three-chart summary for Search, Board, Sprint, Release, and Backlog exports. Despite the name it is an ordinary Exportelier template — if you want to build a report from an actual Jira dashboard, see dashboard import.

See Output formats for how a single template produces PDF, Word and Markdown.

Choose the document mode​

When creating a layout template, choose one document per issue or one document for the whole issue set. The issue-set option starts with a header, a chart across issues and a repeater over the issues. Put single-issue fields, comments and subtasks inside that repeater.

The designer distinguishes single-issue components from whole-set components. A warning on the canvas explains an incompatible position. You can change the mode in the save dialog; it shows how many components are affected. Switching never rewrites the template: review those components yourself before exporting.

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.