Binding components to Jira data
Components show real Jira data by being bound to a field. Binding is how a generic "field" component becomes "Assignee" or "Story points".
Selecting a field source
Select a component on the canvas, then choose the field it should display from the property panel. Standard fields and custom fields both appear in the picker.
A field component selected on the canvas with the property panel showing the field picker.
Standard vs. custom fields
A field-renderer registry knows how to render standard Jira field types and many third-party custom field types. When a field type is not explicitly supported, a safe fallback renders its value as readable text rather than failing the export. See Custom fields.
Formatting values
Where a field supports it, you can control how the value is presented (for example, date formatting or how a user is displayed). The live preview reflects formatting choices immediately.
Binding a Category chart
Bind a Category chart to a field that can be grouped safely, such as Status, Issue type, Priority, Assignee, or Labels. The chart aggregates the current exported issue set; it does not run a saved filter or make another Jira request.
For a single-value field, each issue contributes one assignment. For a multi-value field, each value contributes one assignment, so the percentage denominator is the total assignment count. Empty values are grouped under None. If there are more categories than the configured limit, choose whether to combine the remainder as Other or truncate it with a visible note. Values that cannot be grouped safely are called out visibly rather than dropped.
Binding a Time series
In a normal export template, a Time series reads the current exported issue set. In a report, bind it to one named Saved Filter source. The same source feeds all series in that component; adding more series or changing the bucket interval does not run a Jira query per series or per bucket.
Each series uses one date event: Created, Resolved, or a scalar custom Date or
Date-Time field. Resolved reads only Jira's resolutiondate; a Done status does
not substitute for a missing resolution date.
Remember that a Saved Filter is evaluated when the export runs. Historical buckets use dates from the issues returned now and do not reconstruct which issues matched that filter in the past.
Preview against sample data
The designer previews bindings against realistic sample data, so you can verify a layout before exporting real issues.
If you bind to a field type the registry does not recognize, the value is rendered with the safe fallback instead of breaking the document. Report gaps so coverage can improve — see Field rendering problems.