Preparing Backlog: projects, issue types, and custom fields
Set up Backlog projects, issue types, and custom fields before building forms.
Do this in Backlog once for each project that will receive portal requests. Chronigami can only map a form to a project the ticket bot has joined.
Note
An admin sets up the ticket bot. If you are an editor, ask an admin to finish Setting up the ticket bot before you map a form.
Projects
- Choose the Backlog project where these requests should become issues.
- Confirm the ticket bot is a member of that project. In Chronigami, Manage → your portal → your form → Backlog lists only projects the bot has joined. If the list is empty, you see “The bot hasn't joined any projects yet.”
The form also needs a Priority. Chronigami loads priorities from Backlog after a bot is set.
Issue types
- Open the project's issue type settings.
- Choose an existing issue type, or create one for these requests, for example “Service Request”.
- Note the name. You will select it on the form's Issue type control.
Backlog can attach its own issue-type description templates. Those are separate from the form's Summary and Description templates in Chronigami.
Custom fields
Use a custom field when the answer does not belong in the issue summary or description, such as a department list or a “Requested by” text field.
- Create or reuse the custom field on the project.
- Set which issue types it applies to. Include the issue type this form will use, or apply it to every type.
- Mark it required in Backlog only if every request must supply it. The form must map every required custom field that applies to that issue type, or readiness fails.
Which custom field types you can create depends on your Backlog plan. Chronigami only offers a custom field as a mapping target when its type matches the form field. See Mapping a form to Backlog.
Warning
If a required custom field applies to the issue type and the form does not map it, Backlog will reject the submission. Re-check on the form's Readiness tab reports “A required custom field is not mapped.”
Tip
A custom field with no applicable issue types applies to every type. That is easy to miss when you add a new issue type later.
Permissions for the ticket bot
The bot user's project role must allow adding issues.
Chronigami reads the bot's space role when you save the key. It refuses Viewer. On the form, Re-check fails with “A Viewer cannot create issues” if the live role is Viewer.
The bot also needs to stay on the project. Removing it from the project makes Re-check fail with “The ticket bot has not joined this project.”
Still need help?
Contact supportRelated articles
- Setting up the ticket botCreate the Backlog user that Chronigami uses to create issues from submissions.
- Mapping a form to BacklogChoose the project, issue type, and where each form field goes on the Backlog issue.
- 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.