Users Are Missing From the USER Table

Issue

Some Jira users are missing from the USER table in your destination, or user fields such as active are out of date compared to Jira.

Environment

Connector: Jira

Cause

This is usually expected behavior. Fivetran does not sync every Jira user from a dedicated users endpoint. Instead, we sync users when they appear in other Jira data that we sync. We sync users to the USER table when they are associated with synced issues, projects, comments, or supported user-type fields. For example, we sync users who are:

• The lead of a synced project.
• The reporter, creator, or assignee of a synced issue.
• The author or update author of a synced comment.
• A watcher, approver, or value in a supported user-type field on a synced issue.

If a Jira user is not referenced by data in your connection's sync scope, we cannot discover and sync that user. For example, a user may not appear in the USER table if they only log time in an app such as Tempo Timesheets, has browse-only access, or has no recent issue activity.

Why user fields can become stale

Even when a user is present in the USER table, we only refresh that user's attributes when we sync Jira data that references the user. Jira does not provide a user-change event that we can incrementally track.

For example, if a user is deactivated in Jira but none of the issues that reference the user are updated afterward, the user's active value in your destination can remain stale until a re-sync forces us to reprocess the relevant issues.

Resolution

Run a historical connection re-sync

Run a historical connection re-sync if the user has stale field values. A historical re-sync reprocesses all selected Jira data in the connection, including issues that reference users. This can refresh user records that are tied to synced projects, issues, comments, and supported user-type fields.

To learn how, see How to Trigger Historical Connection Re-Syncs.

A historical re-sync only refreshes users that we can discover through synced Jira data. It does not add Jira users who are outside the connection's sync scope.

Use Connector SDK for missing users

Use Connector SDK if you need a complete or broader Jira user list that is not limited to users referenced by synced issues, projects, comments, or supported user-type fields.

For example, you can build a custom connector that calls the Jira Cloud /rest/api/3/users/search endpoint and loads the results into a separate destination table. This can help with use cases such as:

• Active users who only log time in an app such as Tempo Timesheets.
• Inactive users needed for reconciliation or reference.
• A complete user list from a dedicated Jira users endpoint.

To get started, see our Connector SDK setup guide and Connector SDK tutorials.