2.19.x release notes
What's new
Cleanup of empty groups, Confluence content creation tracking, and improved SCIM compatibility.
Upgrade consideration
No special considerations apply to this update. The new "delete empty groups" option is off by default, so existing behaviour is preserved until you enable it per connector.
Data Center
This version is fully compatible with Jira, Confluence, Bitbucket, and Bamboo Data Center.
Changelog
2.19.1 & 2.19.1-p8
Released on 14 July 2026 for Jira, Confluence, Bitbucket, and Bamboo Data Center and as part of SAML Single Sign-On 6.16.2.
Fixed the SCIM connector ignoring group member removals sent as PATCH
removeoperations with a value filter (e.g. by Okta) while returning 200 OK — deprovisioned users stayed in their groups.Fixed other apps failing to start since 2.19.0. The plugin no longer exposes its embedded Log4j packages.
Updated embedded libraries.
Changes specific to Jira
None
Changes specific to Confluence
None
Changes specific to Bitbucket
None
Changes specific to Bamboo
None
2.19.0 & 2.19.0-p8
Released on 28 May 2026 as a standalone app for Jira, Confluence, Bitbucket, and Bamboo Data Center and as part of SAML Single Sign-On 6.16.0.
Added an option to delete groups that were created by User Sync once they become empty or are filtered out by a sync.
Improved SCIM compatibility: attribute mapping and transformation now handle patch paths with filters and targets, such as
emails[type eq "work"]andmembers[value eq "..."].displayName.The Excel export now writes dates in a human-readable format instead of Unix timestamps.
Fixed an issue where filtered users were always deactivated regardless of the configured cleanup behaviour. Filtering now respects each connector's cleanup setting.
Changes specific to Jira
None
Changes specific to Confluence
Added content creation detection for Confluence users so administrators can identify licensed accounts that have never contributed content.
Changes specific to Bitbucket
None
Changes specific to Bamboo
None