Setting up a form to create Backlog issues

A form becomes useful when every submission creates an issue in Backlog. This guide walks through the whole setup once, from end to end. Each step links to a more detailed article if you need it.

#Before you start

An admin needs to have done these once for the workspace:

1. The workspace has a Portal subscription or trial.
2. A Backlog space is connected. You'll find connected spaces under Workspace settings → General.
3. A ticket bot is set up. This is a dedicated Backlog user whose API key Chronigami uses to create issues. Set it up under Workspace settings → Portal. See Setting up the ticket bot.

#In Backlog: prepare the project

Do this once for each Backlog project that will receive requests. See Preparing Backlog for details.

1. Choose the project where requests should go.
2. Add the bot user to the project. Its role must allow adding issues.
3. Choose or create an issue type for these requests, for example "Service Request," in the project's settings under issue types.
4. Set up custom fields for information that doesn't fit the summary or description, such as a "Department" list or a "Requested by" text field. Make sure each one applies to your issue type.
5. Note any required custom fields that apply to your issue type.

#In Chronigami: connect the form

Open Manage, then your portal, then your form.

#Choose the project and issue type

On the Backlog tab, choose the project, issue type, and priority. Optionally, choose a fixed assignee and people to notify for every request from this form.

#Bind your fields

For each form field, choose where its answer goes in Backlog. Chronigami only offers targets that match the field's type. For example, a date field can go to the start date, the due date, or a date custom field. See Mapping a form to Backlog.

• Choice fields bound to a Backlog list take their options from Backlog, so they always match.
• Fields from the field library can't be bound to a Backlog list. Unlink the field from the library first; it then becomes this form's own field.

#Write the templates

On the Templates tab, write the issue's summary (required) and, optionally, its description. Insert your form's answers with placeholders from the list, then check the preview. See Templates and placeholders.

Placeholders use each field's key. For example, if your form has a field with the key issue_title, the summary template {{issue_title}} puts that answer in the issue's summary. Chronigami also provides {{submitter.name}}, {{submitter.email}}, {{portal.name}}, and {{form.name}}.

#Check readiness

On the Readiness tab, select Re-check. Fix anything marked as failing, then read the setup checklist for the things Chronigami can't check automatically. See Readiness checks.

#Test and publish

1. Submit the form yourself and check that the issue looks right in Backlog: the summary, description, field values, and any attachments.
2. Make it available: make sure both the form and its portal are active.
3. Choose who can use it: a portal can be public (anyone with the link) or members only. See Public and members-only portals.