Readiness checks
Run Re-check, read each result, and fix what blocks a form from creating issues.
Readiness is the stored result of Re-check. Chronigami does not run these checks when you open the tab or the forms list, because each run uses the ticket bot's Backlog rate limit. Press Re-check when you change the bot, the mapping, the templates, or Backlog itself.
Until you run it, the badge is Not checked. After a run it is Ready · checked {when} or {n} issues · checked {when}.
What is checked
- Open Manage → your portal → your form.
- Select the Readiness tab.
- Read Last check, then select Re-check. The button reads Checking… while it runs.
- Read This form is ready or This form isn't ready yet, then each check.
These checks run:
| When it passes | When it fails |
|---|---|
| Ticket bot is set. | Set a ticket bot before mapping this form. |
| The form uses the ticket bot's Backlog space. | Set a ticket bot before mapping this form. / The ticket bot's Backlog space is no longer connected. |
| The ticket bot has joined the mapped project. | Choose a Backlog project. / The ticket bot has not joined this project. |
| The ticket bot can create issues. | A Viewer cannot create issues. |
| The mapped issue type exists on this project. | Choose an issue type. / That issue type is no longer on this project. |
| A priority is set. | Choose a priority. |
| Every mapped custom field applies to this issue type. | A mapped custom field does not apply to this issue type. |
| Every required custom field for this type is mapped. | A required custom field is not mapped. |
| A summary template is set. | Write a summary template. |
| Every template placeholder names a field or a built-in key. | Unknown template keys: {keys}. |
| Bound list options still exist in Backlog. | A mapped list option is no longer in Backlog. |
| Every mapping points to a field on this form. | Mappings refer to missing fields: {keys}. |
| Every mapping is compatible with the field's current type. | Incompatible mappings: {keys}. |
If Backlog cannot be reached, several checks show “Backlog is unavailable.” If no bot is set, they may show “Ticket bot is not set.”
After the checks, Setup checklist lists work Chronigami does not verify:
- Add any extra Backlog watchers beyond the stored notified users.
- Confirm the Backlog space has enough disk for attachments.
- Confirm category names still match how the team creates issues.
- Read the rendered summary and description with sample values.
- Backlog issue-type templates are separate from this form's templates.
- If a list field needs an “Other” value, plan for that in a later release.
A form that passes Re-check can accept submissions. Editors see This form isn't ready yet when it fails. People who submit see “This form isn't available yet.”
Fixing a failed check
Match the failed message, then fix the cause.
| Failed message | What to do |
|---|---|
| Set a ticket bot before mapping this form. | An admin sets the bot. See Setting up the ticket bot. |
| The ticket bot's Backlog space is no longer connected. | An admin reconnects the space under Workspace settings → General → Connected spaces. |
| Choose a Backlog project. / The ticket bot has not joined this project. | Add the bot to the project in Backlog, or choose a project it has joined. See Preparing Backlog. |
| A Viewer cannot create issues. | Change the bot user's Backlog role so it can add issues, or save a different bot. |
| Choose an issue type. / That issue type is no longer on this project. | Pick an issue type that still exists on the project. |
| Choose a priority. | Open Backlog and choose Priority. |
| A mapped custom field does not apply to this issue type. | In Backlog, apply that custom field to the issue type, or map the form field to a different target. |
| A required custom field is not mapped. | Map a form field to that custom field. See Mapping a form to Backlog. |
| Write a summary template. | Open Templates and fill in Summary (required). See Templates and placeholders. |
| Unknown template keys: {keys}. | Fix or remove those placeholders. See Templates and placeholders. |
| A mapped list option is no longer in Backlog. | Restore the option in Backlog, or remap the field. |
| Mappings refer to missing fields: {keys}. | Open Backlog and select Save Backlog mapping so leftover mappings are dropped. |
| Incompatible mappings: {keys}. | Change the field type back, or pick a target that fits the new type. |
Warning
A form that is not ready cannot accept submissions. People who try see “This form isn't available yet.”
Rechecking
Select Re-check after you change any of the following:
- The ticket bot, its role, or its project membership
- Project, Issue type, Priority, or Field mapping
- Summary (required) or Description
- A field key, a field type, or a field from the Field library
- Custom fields, issue types, or list options in Backlog
The new result overwrites Last check. Opening the tab again does not rerun the checks; you see the stored badge until you press Re-check.
Still need help?
Contact supportRelated articles
- Mapping a form to BacklogChoose the project, issue type, and where each form field goes on the Backlog issue.
- Templates and placeholdersWrite the issue summary and description from form answers and built-in keys.
- Setting up the ticket botCreate the Backlog user that Chronigami uses to create issues from submissions.
- 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.