SharePoint Connector for Jira: Version History Support in SharePoint

SharePoint Connector for Jira: Version History Support in SharePoint



Problem Statement:


When a file is uploaded to Jira and added to SharePoint via the SharePoint Connector, subsequent edits made through the Jira Service Management (JSM) Customer Portal do not appear in the SharePoint document version history as expected. Specifically, users were unable to see detailed version logs or the identity of editors in SharePoint, similar to the standard check-in/check-out process. The concern is whether the connector supports version tracking for files edited via Jira, and how SharePoint permissions settings affect this behavior.

 

Application

  • Atlassian Platform: Jira Cloud

  • Product: SharePoint Connector for Jira

  • Environment: Cloud

 

Solution

  1. Version History Behavior

    • The SharePoint Connector for Jira does support version history in SharePoint for files uploaded and edited via Jira or Confluence.

    • The visibility and detail of version history in SharePoint depend on the "Replicate Permissions" setting in the connector configuration.

  2. Replicate Permissions Setting

    • Replicate Permissions ON:

      • Each edit to a file is logged in SharePoint with the actual user’s name (if the user has a SharePoint account).

      • The SharePoint version history will show who edited each version.

    • Replicate Permissions OFF:

      • All edits are logged as being made by the SharePoint user who connected the base folder to Jira/Confluence.

      • Version history will still show multiple versions, but all changes will appear as if made by a single user (the connector account).

      • This mode allows users without SharePoint accounts to edit files, but individual user actions are not tracked in SharePoint.

  3. Troubleshooting Steps

    • If version history is not visible in SharePoint:

      • Confirm that SharePoint versioning is enabled in the target document library.

      • Check the "Replicate Permissions" setting in the SharePoint Connector for Jira configuration.

      • If "Replicate Permissions" is OFF, expect all edits to be attributed to the connector account.

      • If "Replicate Permissions" is ON and user edits are still not tracked, review SharePoint library permissions and connector setup.

  4. Best Practice Recommendation

    • Enable "Replicate Permissions" if you require detailed version history with individual user attribution in SharePoint.

    • Ensure SharePoint library versioning is enabled for full tracking.

References

  • For visual guidance, refer to the screenshots provided in the ticket for SharePoint version history menu options.

  • image-20260311-165633.png
  • image-20260311-165712.png