Syncing Assignees Between Jira and Rootly Action Items
Last updated: March 24, 2025
When updating assignees between Jira and Rootly action items using workflows, you'll need to use the correct custom field mapping syntax to ensure proper synchronization.
Updating Rootly Assignees from Jira
To update a Rootly action item's assignee when the Jira assignee changes, use this custom fields mapping in your workflow:
{
{% assign user_id = team.users | find: 'name', alert.data.issue.fields.assignee.displayName | get: 'id' %}
"assigned_to_user_id":"{{ user_id | default: "unset" }}"
}
This mapping will:
Find the Rootly user that matches the Jira assignee's display name
Get their internal Rootly user ID
Set them as the assignee, or unassign if no matching user is found
Updating Jira Assignees from Rootly
When updating the Jira assignee from Rootly changes, use the Jira assignee's email address or display name in your workflow configuration. The exact field to use may depend on your Jira configuration.
The user names must match exactly between Rootly and Jira for the synchronization to work properly. Make sure usernames are consistent across both systems.
Unassigning Users
To remove an assignee:
In Rootly: Clear the assignee field (leave it blank)
In Jira: Set the assignee to "Unassigned"
The synchronization will maintain the unassigned state between both systems when configured correctly.