Jira Merge Fields

Jira Merge Fields

Jira merge fields let you embed live Jira issue data directly into your contract templates. When a Sender creates a contract from your template, E-SignSeal resolves each field chip against the linked Jira issue → the resulting document is pre-populated with real values before it reaches the signers.

Jira Fields panel in template editor showing all standard field chips

Jira Fields panel in template editor showing all standard field chips

How merge fields work

In the template editor, merge fields appear as colored chips (for example {{Summary}}). In the rendered contract and the generated PDF, those chips are replaced with the actual Jira field value from the linked issue. If a field has no value on the issue (for example, Due Date is blank), the chip resolves to an empty string — no visible placeholder remains.

Standard fields

The following fields are available on every template, regardless of project or issue type.

Field name

Token

Example resolved value

Issue Key

{{Issue Key}}

LEGAL-104

Summary

{{Summary}}

Vendor Onboarding — Acme Corp

Description

{{Description}}

Full issue description text

Assignee

{{Assignee}}

Jordan Lee

Reporter

{{Reporter}}

Sam Patel

Priority

{{Priority}}

High

Status

{{Status}}

In Progress

Project Name

{{Project Name}}

Legal Operations

Project Key

{{Project Key}}

LEGAL

Issue Type

{{Issue Type}}

Contract

Created Date

{{Created Date}}

01 Jul 2026

Due Date

{{Due Date}}

31 Aug 2026

Custom fields

If your Jira admin has created custom fields, they appear at the bottom of the Jira Fields panel under Custom fields. Custom field chips follow the same {{Field Name}} format.

Custom fields are resolved from the linked issue at send time. If a custom field is deleted in Jira after a template was saved, the chip renders as an empty string in new contracts but does not break existing sent contracts (which already have their values baked in).

Inserting a field

  1. Place the cursor at the position in the template where you want the field value to appear.

  2. In the Jira Fields panel on the right, select the chip for the field you want.

  3. The chip appears inline in the editor at the cursor position.

You can also type a field chip directly: type {{ and begin typing the field name. The editor provides an autocomplete dropdown.

Formatting rules

  • Date fields ({{Created Date}}, {{Due Date}}) resolve using the format DD MMM YYYY — for example, 01 Jul 2026. This format is fixed and does not inherit the Jira instance locale setting.

  • {{Description}} preserves line breaks from the issue description. Formatted descriptions (bold, lists) are stripped to plain text.

  • Fields that resolve to an empty string leave no visible gap in the rendered contract — the surrounding text flows as if the chip were not there.

  • Merge fields are case-sensitive in the template editor. {{summary}} is not the same as {{Summary}}.

Using merge fields in headings

You can insert merge fields inside heading elements. For example, placing {{Summary}} inside an H1 heading produces the issue summary as the document title in the rendered contract.

Previewing resolved values

The template editor does not show resolved values — field chips remain visible during editing. To preview a fully rendered contract, create a test contract from your published template against a real Jira issue and review it on the Document tab of the contract detail.

Next steps