この記事はまだ日本語に翻訳されていないため、英語で表示しています。
Templates and placeholders
Write the issue summary and description from form answers and built-in keys.
The Templates tab writes the Backlog issue's summary and description. Placeholders insert a form answer or a built-in value. Check the Preview before you save.
Summary template
- Open Manage → your portal → your form.
- Select the Templates tab.
- In Summary (required), write the issue summary. Insert a placeholder from Form fields or Built-in (it goes where the cursor is).
- Select Save templates.
The summary cannot be empty. The UI refuses save with “A summary template is required.” Backlog summaries are limited to 255 characters; Chronigami trims anything longer.
Submissions and Re-check both require a summary template. A form with no summary cannot create issues.
Description template
Description is optional.
- If you write a template, Chronigami renders it and sends that text as the issue description.
- If you leave it empty, Chronigami lists every answered field as
Label: value, one per line. Empty answers are omitted.
ヒント
Put structured answers in mapped Backlog fields. Use the description for the story of the request. See Mapping a form to Backlog.
Add to description on the Backlog tab is a mapping target for some field types. It does not replace this template. Unmapped answers still appear here if you leave Description empty or include their placeholders.
Available placeholders
Placeholders use double braces around a field key: {{issue_title}}. The key is independent of the label. You see both in Form fields as {{key}} and the label.
Built-in placeholders:
| Placeholder | What it inserts |
|---|---|
{{submitter.email}} | Submitter's email |
{{submitter.name}} | Submitter's name |
{{portal.name}} | Portal name |
{{form.name}} | Form name |
On a public portal, {{submitter.name}} and {{submitter.email}} are empty unless the person is signed in. Add form fields if you need a name or email on every request.
The Preview fills field placeholders with <Label> when you have not typed a sample, and uses your signed-in name and email for the submitter keys. Unknown keys appear as “Unknown placeholder: {{key}}.”
警告
A placeholder that does not match a field key or a built-in key fails readiness: “Unknown template keys: key.” Fix the spelling or change the field key, then Save templates and re-check readiness.
Renaming a field's label does not break placeholders. Changing the field key does.
解決しませんか?
サポートに問い合わせる関連記事
- Mapping a form to BacklogChoose the project, issue type, and where each form field goes on the Backlog issue.
- Readiness checksRun Re-check, read each result, and fix what blocks a form from creating issues.
- Setting up a form to create Backlog issuesThe end-to-end steps to connect a portal form to a Backlog project, from preparing Backlog to making the form available.