Messages that block publishing a template are listed in Publishing checks.
No process template you may start applies to this page. Check in the designer: the template is published; its Scope includes this space; Who may start and end this process includes you; and if it starts On a page event, Also allow a manual start is ticked.
Click Check again. If the ticket is in a status that Jira puts in the category In Progress (for example “In review”), it does not count as done — ask a space admin to tick that category or move the ticket to a Done status.
The ticket was deleted, moved to another project, or the project’s permissions changed. The document waits. Restore the ticket’s access, or continue anyway.
The step went through, but the ticket was not created — the message says why (usually permissions or a mandatory field). The gate stays closed for the missing required ticket. Fix the template and continue anyway, or end the process and start again.
Someone else clicked at the same time. The panel is refreshed; look and try again.
An automatic fork has no line for the current state. Ask the template owner to add one, or an Otherwise branch.
You are not among the people the space settings allow to continue anyway.
LINA cannot see restricted pages. See Permissions.
Reload the template before saving, otherwise you would overwrite their changes.
Ask a Confluence admin to set it, or leave Service account empty — LINA then creates the tickets.
Remove it from the templates that use it first. The designer names them.
The form reads Jira with the rights of the template’s service account (after Save), or LINA’s when there is none. Projects the account cannot create issues in are not offered.
Space settings open only for admins of that space.
The defaults apply there: tickets count as done in the Done category, space admins may continue anyway.
The sample creates its ticket only in a project where you can create issues. Choose another project, or tick No Jira — run the sample without a ticket.