Mapping a form to Backlog
Choose the project, issue type, and where each form field goes on the Backlog issue.
On the form's Backlog tab you choose the project that receives submissions and where each answer goes on the issue. Chronigami only offers targets that match the field's type.
Note
If you see No ticket bot is set up yet, an admin must finish Setting up the ticket bot first. The button Open workspace settings, Portal tab opens that screen.
Choose the project and issue type
- Open Manage → your portal → your form.
- Select the Backlog tab.
- Choose the Project. The list shows projects the ticket bot has joined, as
Name (PROJECTKEY). If the list is empty, you see “The bot hasn't joined any projects yet.” See Preparing Backlog. - Choose the Issue type.
- Choose the Priority. Re-check fails without one.
- Select Save Backlog mapping.
Changing Project clears Issue type, Assignee (fixed), Notify these people, and mappings that depend on that project (categories and custom fields). Mappings to Add to description, Start date, Due date, and Attachment stay.
Map fields
Under Field mapping, each form field has a target. Not mapped means the answer is not sent to a dedicated Backlog field. It can still appear in the issue description through the description template.
The helper text on the tab is: “Only Backlog targets that fit each field's type are offered. Choice fields mapped to a Backlog list take their options from Backlog.”
| Form field type | Targets you can choose |
|---|---|
| Short text, Long text, Email | Add to description, or a text or sentence custom field (Custom field: {name}) |
| Number | A number custom field only |
| Date | Start date, Due date, or a date custom field |
| Dropdown | Category, or a single-list or radio custom field |
| Multi-select | Categories, or a multiple-list or checkbox custom field |
| Checkbox | Category, or a list, checkbox, or radio custom field. Then Choose the Backlog item — checking the box sets that item |
| File upload | Attachment |
A Dropdown or Multi-select bound to Category, Categories, or a list custom field takes its options from Backlog. Edit those options in Backlog, not on the form.
A field from the Field library cannot take options from a Backlog list. If you map one that way, Chronigami shows: “A field from the Field library keeps the library's options, so it can't take its options from a Backlog list. Unlink it from the library first.” Select Unlink from library. The field stays on this form with its current label, type, and options. Then save the mapping again.
Note
A Number field cannot use Add to description. Create a number custom field on the project if you need that answer on the issue.
Default values
These apply to every issue this form creates. They are optional.
- Assignee (fixed) — choose a project member, or Nobody to leave the issue unassigned.
- Notify these people — check the Backlog users who should be notified of every request. Choose a project first; until then you see “Choose a project first.”
- Select Save Backlog mapping.
To see who else should watch the issue, use the Setup checklist on Readiness. That list is not stored on the form.
When the mapping and templates look right, run Re-check. See Readiness checks.
Still need help?
Contact supportRelated articles
- Preparing Backlog: projects, issue types, and custom fieldsSet up Backlog projects, issue types, and custom fields before building forms.
- Templates and placeholdersWrite the issue summary and description from form answers and built-in keys.
- 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.