Connect and route projects
You need an Atlassian account with access to the service projects you want Fini to handle, and a Fini agent with the appropriate knowledge and instructions.1
Connect Jira
Click Connect Jira, sign in to Atlassian, and authorize one Jira Service Management site with all requested permissions. These include issue-write and user-read access, alongside service-request, webhook, and offline access. Back in Fini, confirm Connection details shows the expected site and Connected.
2
Map projects to agents
Under Bot routing → Bot and project mapping, select a bot and one or more projects. Project labels include their name, key, and ID. Projects without an assigned bot are excluded from processing.
3
Save routing
Click Save changes. Each route must have a bot and at least one project. Saving routing is separate from connecting the site.
4
Choose reply behavior
Click Go to Reply Behavior Settings. Use Jira as the source and, when needed, a Jira project condition to scope the rule. Start with internal notes if your team wants to review recommendations before enabling customer-facing replies.
How replies work
Fini processes eligible Jira requests in mapped projects. Public reply outcomes create customer-visible comments; recommendation outcomes create internal notes. No reply suppresses a response. Routing alone does not override Reply Rules. Before sending, Fini rechecks that the request is not closed, still belongs to the routed project, and is not owned by a human in Fini. Test these conditions with a non-production request before rolling out customer replies. Jira is also available in the shared source filters used to find conversations. Use Inbox and AI Steps to inspect the selected agent, reply rule, and result.Use Jira custom fields as attributes
In Attributes, use the Jira Ticket group and Custom expression to map a custom field into a configured attribute. Paths use the Jira field ID, not its display name:ticket.customFields.customfield_12345for a scalar value.ticket.customFields.customfield_12345.valuefor an option object.ticket.customFields.customfield_12345[0].valuefor the first option in a list.
Map Fini tags to Jira labels
Use Fini tags → Jira labels on Deploy → Jira to map output tags to one or more Jira issue labels. The section is available after connecting Jira and is hidden when the connection requires reconnection.1
Choose an output tag
Click Add your first tag mapping (or Add tag mapping for another mapping), then use Select Fini tag. If no output tags are available, create them in Tags first.
2
Add Jira labels
Enter a label such as
needs-review and press Enter or click the plus button. Repeat for additional labels, then click Add Mapping. Labels cannot contain whitespace.3
Save the mappings
Click Save Tag Mappings. This saves label mappings separately from project routing.
Verify the connection
Create or update a test request in a mapped service project. Confirm it appears in Fini, uses the intended agent, and produces the expected public comment, internal note, or no-reply outcome. An unmapped project should not be handled. A connected account alone does not prove webhook delivery and reply permissions are working. If you configured label mappings, use a test request that selects a mapped output tag. Confirm the mapped labels appear in Jira and any existing labels remain.Why Jira isn’t working
Jira labels are not appearing
Jira labels are not appearing
Confirm the connection is authorized, the mapping was saved with Save Tag Mappings, and Fini selected the mapped output tag. Check that the label contains no whitespace and that the connected account can edit the issue. A closed issue or one moved to another project is skipped. A successful reply alone does not prove label sync succeeded.
No accessible service projects
No accessible service projects
Check the connected Atlassian account’s Jira permissions. Only accessible service projects are listed. Click Try again after fixing access.
Routing says Needs attention
Routing says Needs attention
The saved webhook state is missing or expired. The page asks you to reconnect Jira to restore processing; saving project mappings does not repair authorization or renew a broken connection.
The connection says Reconnect required
The connection says Reconnect required
Authorization could not be refreshed. Use Disconnect Jira, confirm the disconnect, then connect again and verify project routing.
The request is visible but no customer reply was sent
The request is visible but no customer reply was sent
Check Reply Rules first: the outcome may be an internal note or no reply. Also check whether the request is closed, moved to another project, or has been taken over by a human in Fini.

