Atlassian Release Notes

All Atlassian Release Notes

• Nov 6, 2025

  • Parsed from source:
    Nov 6, 2025
  • Detected by Releasebot:
    Nov 6, 2025
  

  Jira by Atlassian

  Jira Software 11.2

  Jira Software 11.2 brings OpenSearch support for Data Center, a 10k board item limit, safeguards and optimizations for admins, OAuth 2.0 app links, JQL resilience, a React/Atlaskit upgrade, and a consolidated cleanup via Instance Optimizer. It tightens admin permissions.

  We’re pleased to present Jira Software 11.2.

  Highlights

  • Welcome OpenSearch in Jira Data Center
  • New limit of 10,000 items on a board
  • Optimize your instance with safeguards
  • Optimize your custom fields
  • One place to clean them all
  • Strengthen sysadmin and OS access separation
  • Protect you Jira nodes with JQL resilience
  • Connect securely with OAuth 2.0 for app links
  • Rate limiting now supports OAuth 2.0
  • Deprecation of Browse Project properties in workflows
  • Indexing and snapshots improved with OpenSearch
  • Handle large tables with Cluster message cleaning service
  • React 18 and Atlaskit upgrade in Jira 11.2
  • Changes to supported platforms
  • App developers
  • Upgrade procedure
  • Resolved issues

  Welcome OpenSearch in Jira Data Center

  For:
  END USERS
  ADMINS

  With the Jira Data Center 11.2 release, OpenSearch is fully supported for production use. You can now configure Jira to use OpenSearch as your search platform, either on premises or as a managed service like AWS OpenSearch Service.
  Explore how to configure OpenSearch for Jira
  We recommend switching to OpenSearch because it offers performance, scalability, and reliability improvements over Lucene.
  To understand the differences between OpenSearch and the default Lucene search platform, review the OpenSearch for Confluence Data Center guide. While this guide focuses on Confluence, the information about the search platforms is also relevant for Jira. We're working on a Jira-specific report and will share it as soon as it's ready.
  You might also want to get familiar with our previous OpenSearch documentation:

  • Search API deprecations and upgrade guide for Jira 11
  • Migrating FieldIndexers in Jira 11
  • Migrating Lucene collectors to Search API in Jira 11

  New limit of 10,000 items on a board

  For:
  END USERS
  ADMINS

  This limit applies only when you’re using OpenSearch. The default Lucene search platform isn’t affected, but you can also configure Lucene to enforce the same limit.
  With the OpenSearch implementation in Jira, Scrum and Kanban boards can display up to 10,000 items. When a board is full, an admin needs to update the board filter to reduce the number of included issues. This update helps Jira scale for large enterprises, improves search performance, and prevents indexing bottlenecks.
  To check the total number of issues on your board, go to Issues, then select Search for issues and apply your board’s filter. By default, you can view up to 10,000 issues. An admin can override this limit by setting the jira.search.platform.max.result.window property.
  More about issue display limits on boards

  Optimize your instance with safeguards

  For:
  ADMINS

  Jira Instance Optimiser now includes safeguards to help you stay within recommended limits for comments, custom fields, issue types, issues, and projects. These safeguards help maintain system stability and performance as your instance grows.
  To set up the limits:

  1. In the upper-right corner of your Jira application, select Jira administration, and then select System.
  2. In the sidebar, find Instance Optimizer and select Overview.
  3. Select Configure safeguards.
     You can enable or disable safeguard enforcement, and choose whether to receive email and in-app notifications. When usage approaches a set limit, system admins receive notifications. If a user tries to perform an action that would breach a safeguard, the action is blocked and the user receives a warning.
     Explore how to configure safeguards in Instance optimizer

  Optimize your custom fields

  For:
  ADMINS

  Instance optimizer now makes it easier to manage your custom fields. You can search, filter, and take bulk actions, including deleting custom fields directly from the recommendations page. You can also see more details about custom field usage and the impact of localizing these fields.
  You can scan your custom fields to identify those with configurations that can be optimized. If your last scan is more than 24 hours old, you will need to re-scan to ensure you have the most up-to-date data. After 24 hours, previous scan results are no longer displayed.
  Optimize your custom fields in Jira

  One place to clean them all

  For:
  ADMINS

  We're deprecating the Clean up functionality in Jira Data Center and removing the Audit Custom Fields link. Instead, the cleanup features, such as project and issue archiving, are now integrated into the preinstalled Instance Optimizer app, which provides more efficient and automated ways to optimize your instance.
  With this change, you’ll find all the cleanup features in one place.
  More about Instance Optimizer for Jira

  Strengthen sysadmin and OS access separation

  For:
  ADMINS

  Starting from Jira 11.2, we’ve clarified the distinction between the global administrative permissions: Jira administrator and Jira System administrator and introduced new application properties. You can use them to ensure that only users with the highest level of administrative access can perform sensitive operations.
  In Jira 11.2, the stricter permissions are opt-in, but they'll become opt-out in a future major version of Jira Data Center.
  System administrators can update these properties in the advanced settings in Jira. By default, they’re set to false and let you opt in to the updated role requirements at your own pace. You can test them by setting the property value to true. Enable each property individually to apply stricter permissions

  Protect you Jira nodes with JQL resilience

  For:
  ADMINS

  We’re introducing JQL resilience, a set of safeguards that help prevent node crashes caused by resource-intensive JQL operations. To stop a JQL query from using too much memory or running for too long, you can:

  • set a maximum search result limit.
  • define a JQL query time limit to interrupt queries that run too long.
  • enable a memory usage circuit breaker to reject new JQL queries when memory is low.
    For each node, you can control these limits in the jira-config.properties file. Each change requires you to restart Jira for it to take effect.
    Explore how to use JQL resilience
    When these features are enabled, some JQL searches might return a SearchException in situations you didn’t encounter before, such as timeouts. Jira logs these events and publishes them in the audit log. Use these features only when the risk of node crashes outweighs the impact of failed queries.

  Connect securely with OAuth 2.0 for app links

  For:
  ADMINS

  We’ve added OAuth 2.0 support for application links (app links) across Atlassian Data Center products. OAuth 2.0 is an industry-standard authentication protocol that enables secure mand reliable connections between Atlassian products and external applications.
  More about creating applinks
  We’re also working on OAuth 2.0-based app links to connect with cloud to allow for secure and efficient integrations of hybrid environments, and will share the timeline soon.

  Rate limiting now supports OAuth 2.0

  For:
  ADMINS

  Rate limiting in Jira now supports OAuth 2.0 2-legged (2LO) authentication. This update lets you configure rate limits for OAuth 2.0 requests separately from other API requests, making it easier to manage integrations like the Rovo connector.
  More about rate limiting in Jira

  Deprecation of Browse Project properties in workflows

  For:
  ADMINS

  Starting in Jira 11.2.0, we're deprecating the jira.permission.browse.* workflow step properties. These properties are used to restrict issue visibility on certain workflow steps.
  Alternatively, you can set the issue security levels and automation rules to control which users can access the issue based on their project role and the current issue status.
  Update your workflows to use the alternative functionality
  To preview the Browse Project removal enforcement, you can enable the com.atlassian.jira.workflow.permission.browse.removal feature flag. Jira permission manager will ignore these Browse Project properties starting from version 12.0.0.

  Indexing and snapshots improved with OpenSearch

  For:
  ADMINS

  When OpenSearch is enabled in Jira Data Center, you’ll notice changes to both the user interface and REST APIs. The Index Admin UI now uses a new URL (OpenSearchIndexAdmin.jspa) and offers a different set of configuration options tailored for OpenSearch.
  The indexing and snapshot API endpoints now reflect OpenSearch-specific behavior.

  • The reindex endpoint always performs a full background reindex:
    • /jira/rest/api/2/reindex
  • The snapshot endpoints are disabled because they don’t apply to OpenSearch:
    • /rest/api/2/index-snapshot
    • /rest/api/2/cluster/index-snapshot/{nodeId}

  Handle large tables with Cluster message cleaning service

  For:
  ADMINS

  The Cluster message cleaning service now deletes expired rows in batches of 100,000, making it easier to manage very large tables, even up to 100 million rows. This update prevents database strain by avoiding single, large transactions that could cause memory or disk issues.
  Configure Cluster message cleaning service in Jira

  React 18 and Atlaskit upgrade in Jira 11.2

  For:
  ADMINS

  In Jira 11.1, we upgraded React to version 18 and updated Atlaskit components to their latest versions for Platform packages, Jira Service Management, and Assets. In Jira 11.2, these upgrades have now been applied across the rest of Jira. This change reduces vulnerabilities inherited from older Atlaskit packages and brings recent bug fixes and accessibility improvements to Jira.
  As part of this update, some React web resources have been deprecated. If your custom apps or integrations rely on these resources, check out the recommended replacements for improved performance.
  More about Web Resource deprecation and replacements

  Supported platforms changes

  In Jira 11.2, support for Microsoft SQL Server 2019 (MSSQL 2019) is deprecated.
  For the list of supported platforms, see Supported platforms.
  For previous announcements, see End of support announcements.

  App developers

  See Preparing for Jira 11.2 for any important changes regarding apps.

  Upgrade steps

  Upgrading from Jira version 10.x.x?

  • See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps.
  • For a more tailored upgrade, go to Jira administration, Applications, then Plan your upgrade. We’ll recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.

  Resolved issues

  See the full list of the issues we’ve resolved throughout the lifecycle of Jira Software 11.2.

  Issues resolved in 11.2.0
  Released on 6 November 2025
  [Table of resolved issues with keys, summaries, and statuses, including bugs fixed and improvements made]

  Last modified on Nov 6, 2025

  Original source Report a problem

  Show more
• Nov 4, 2025

  • Parsed from source:
    Nov 4, 2025
  • Detected by Releasebot:
    Nov 5, 2025
  

  Confluence by Atlassian

  Confluence 9.2.10

  Confluence 9.2.10 is a bug-fix release that enhances stability and fixes issues in editing, table formatting, and permissions. This update resolves notable problems in Page View and merged columns, delivering a smoother collaboration experience. Upgrade with backups of the confluence-home and database.

  Confluence 9.2.10 bug-fix release

  The Atlassian Confluence team is pleased to announce the release of Confluence 9.2.10, which is a bug-fix release.

  Don't have Confluence 9.2 yet?

  Check out the new features and other highlights in the Confluence 9.2 release notes.

  Get the latest version

  We recommend you read the Confluence 9.2 release notes and you back up your confluence-home directory and database before upgrading.

  Issues resolved in 9.2.10:

  • CONFSERVER-101131: Favourite Pages Macro queries all available labels and causes inefficient permission checks (Bug, High priority, Fixed)
  • CONFSERVER-100025: Editing pages after disabling and reenabling collaborative editing may cause the most recent published version saved while CE was disabled to not display (Bug, Medium priority, Fixed)
  • CONFSERVER-101312: Table Formatting breaks/misalignment in Page View Mode for Merged Columns. (Bug, Low priority, Fixed)
  • CONFSERVER-101169: Table formatting breaks for some of view mode copied tables. (Bug, Low priority, Fixed)

  Last modified on Nov 4, 2025

  Original source Report a problem

  Show more
• Nov 4, 2025

  • Parsed from source:
    Nov 4, 2025
  • Detected by Releasebot:
    Nov 5, 2025
  

  Confluence by Atlassian

  Confluence 10.1.1

  Confluence 10.1.1 arrives as a bug fix release addressing slow page loads and a wide set of editor, table, and attachment issues. Upgrade guidance points to the new 10.1 features and reminds users to back up data before upgrading.

  Confluence 10.1.1 Release Notes

  The Atlassian Confluence team is pleased to announce the release of Confluence 10.1.1, which is a bug-fix release.

  Don't have Confluence 10.1 yet?

  Check out the new features and other highlights in the Confluence 10.1 release notes.

  Get the latest version

  We recommend you read the Confluence 10.1 release notes and you back up your confluence-home directory and database before upgrading.

  Issues resolved in 10.1.1 include:

  • CONFSERVER-101162: Johnson page is slow to load (Bug, Highest priority, Fixed)
  • CONFSERVER-101131: Favourite Pages Macro queries all available labels and causes inefficient permission checks (Bug, High priority, Fixed)
  • CONFSERVER-100831: Attachment preview fails for copy-pasted duplicate links over time; links show "File does not exist" (Bug, Medium priority, Fixed)
  • CONFSERVER-100350: Importing ICS file with multiple Jira Event Types would only import the first event type, where the rest are omitted (Bug, Medium priority, Fixed)
  • CONFSERVER-99603: Editing Mode Automatically Scrolls Up When Using a Firefox or Chrome Browser (Bug, Medium priority, Fixed)
  • CONFSERVER-101312: Table Formatting breaks/misalignment in Page View Mode for Merged Columns. (Bug, Low priority, Fixed)
  • CONFSERVER-101169: Table formatting breaks for some of view mode copied tables. (Bug, Low priority, Fixed)
  • CONFSERVER-100937: Confluence editor and view does not show the same colors for legacy content (Bug, Low priority, Fixed)
  • CONFSERVER-100908: When editing is restricted on a space home page, re-ordering immediate child pages is not possible for a non-admin user. (Bug, Low priority, Fixed)
  • CONFSERVER-100857: Space Export to PDF function in Confluence, where links in the exported PDF no longer navigate within the document but instead open web links (Bug, Low priority, Fixed)
  • CONFSERVER-100544: Office Word Macro not listing Attachments from Page (Bug, Low priority, Fixed)
  • CONFSERVER-100538: Velocity allowlist error for org.apache.commons.lang3.StringUtils (Bug, Low priority, Fixed)
  • CONFSERVER-99832: Not able to edit a file containing non-Latin and umlaut characters using the Office Connector macro (Bug, Low priority, Fixed)
  • CONFSERVER-99659: Mixed Language Problem in Confluence Draft Notifications with Non-English Language is selected from the profile. (Bug, Low priority, Fixed)
  • CONFSERVER-99484: When scrolling a page, the title overlaps (Bug, Low priority, Fixed)

  Last modified on Nov 4, 2025

  Original source Report a problem

  Show more
• Oct 7, 2025

  • Parsed from source:
    Oct 7, 2025
  • Detected by Releasebot:
    Oct 19, 2025
  

  Confluence by Atlassian

  Confluence 10.1

  Confluence 10.1 brings a powerful Data Center release with OAuth 2.0 app links, service accounts for secure automations, and a React 18.3/Atlaskit upgrade. OpenSearch option, TinyMCE 7.9.1 editor, enhanced macro usage reporting, and clear upgrade steps headline this admin focused update.

  We're excited to present Confluence 10.1

  Highlights

  • Find and sort most used macros in your site
  • Manage your integrations and automations with service accounts
  • Connect securely with OAuth 2.0 for app links
  • Upgrade to React 18.3 and latest Atlaskit
  • OpenSearch for Confluence Data Center
  • Editor upgrade to TinyMCE 7.9.1
  • Supported platforms changes
  • End of support announcements
  • App developers
  • Upgrade steps
  • Resolved issues

  This Confluence release supports only Data Center licenses. If you have a Server license, check out your options for upgrading.

  More

  Read the full list of issues for important info about the resolved issues in this release.

  Thanks for your feedback
  Thanks for your feedback
  More than 314 votes satisfied!

  Find and sort most used macros in your site

  For: ADMINS
  We’ve improved the Macro usage reporting to help you make informed decisions about your macros. Now, you can see which macros are used most often, grouped by app, and easily distinguish between Atlassian and third-party macros. You’ll also find direct links to manage third-party apps in the Universal Plugin Manager (UPM).
  These updates make it easier to identify underused apps, plan for cloud migration, and troubleshoot performance issues. You no longer need to run manual database queries or raise support tickets just to understand macro and app usage across your site.
  To see how often a macro is used, go to the Administration menu, then General Configuration, then Macro Usage. More about macros

  Manage your integrations and automations with service accounts

  For: ADMINS
  Service accounts are specialized, non-user accounts created for secure and efficient management of automated processes and external integrations. With service accounts, you can securely access REST APIs using the OAuth 2.0 authentication method to execute scripts and run tasks while maintaining full control of permissions. All actions performed by service accounts are tracked, providing visibility into their operations.
  To set up a service account:

  • Go to Administration, then User management, then from the sidebar select Service accounts.
  • Select Create service account.
  • Follow the prompts to configure your service account’s details, scopes, and resources.
  • Generate your OAuth 2.0 credentials.
  • Review all the details and copy your credentials to a safe place.
    Explore how to manage a service account

  Connect securely with OAuth 2.0 for app links

  For: ADMINS
  We're introducing OAuth 2.0 support for application links (app links) across Atlassian Data Center products. OAuth 2.0 is an industry-standard authentication protocol that enables secure, modern, and reliable connections between Atlassian products and external applications.
  We’re also working on OAuth 2.0-based app links to connect with cloud to allow for secure and efficient integrations of hybrid environments, and will share the timeline soon.
  Explore how to link to another application

  Upgrade to React 18.3 and latest Atlaskit

  For: ADMINS
  We're upgrading Confluence Data Center to use React 18.3 and the latest Atlaskit components. This update helps keep your instance secure and compliant by enabling ongoing security updates and bug fixes from Atlaskit and React.

  Editor upgrade to TinyMCE 7.9.1

  For: ADMINS
  We’ve upgraded the Rich Text editor in Confluence to TinyMCE 7.9.1. This update brings the latest security enhancements, bug fixes, and improvements to your editing experience in pages and comments. No action is needed — your content and macros remain fully compatible, and the upgrade is applied automatically.

  OpenSearch for Confluence Data Center

  As your Confluence site grows, you need a search that keeps up with your team’s pace. That’s why Confluence Data Center now offers OpenSearch as an opt-in alternative to the default Lucene search platform.
  We recommend switching to OpenSearch because it offers performance, scalability, and reliability improvements over Lucene.
  We’re sharing a guide that explains the benefits of using OpenSearch as an alternative to the default Lucene search platform in Confluence Data Center. It includes:

  • Key differences between OpenSearch and Lucene
  • Benchmark results that show OpenSearch delivers faster search and better scalability
  • Guidance on when and why to switch, with further configuration steps
    Explore the full documentation for more details and performance test results

  Supported platforms changes

  There are no platform changes in this version.
  See the complete list of supported platforms

  End of support announcements

  There are no advance announcements this time.
  For more information on these notices, see End of Support Announcements for Confluence.

  App developers

  Head to Preparing for Confluence 10.1 to find out more about changes under the hood.

  Upgrade steps

  Always test the upgrade in a test environment before upgrading in production.
  To upgrade Confluence to the latest version:

  • From the Administration menu, select Manage apps, and then Confluence update check to verify the compatibility of your user-installed apps with the target application version.
  • From the Administration menu, select General Configuration, and then Plan your upgrade and the version you want to upgrade to. This will run the pre-upgrade checks.
  • From the Administration menu, select General Configuration, and then Troubleshooting and support tools to check your license validity, application server, database setup, and more.
  • If your version of Confluence is more than one version behind, read the release notes and upgrade guides for all releases between your version and the latest version.
  • Back up your installation directory, home directory, and database.
  • Download the latest version of Confluence.
  • Follow the instructions in the Upgrade Guide.

  Update configuration files after upgrading

  The contents of configuration files such as server.xml, web.xml, setenv.bat / setenv.sh, and confluence-init.properties change from time to time.
  When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation; otherwise you will miss out on any improvements we have made.

  Upgrade instructions

  Follow the usual upgrade instructions to upgrade your site.

  Been a while since your last upgrade? Check out our upgrade matrix for a bird's-eye view of the most important changes since Confluence 9.2 LTS.
  Don't forget to renew your software maintenance. Renew now

  Resolved issues

  For full details of bugs fixed and suggestions resolved, head to our public issues tracker on Jira.

  Issues resolved in 10.1.0
  Released on 07 October 2025
  Showing 20 out of 43 issues

  Credits

  Our wonderful customers...
  You play an important role in making Confluence better. Thanks to everyone who participated in interviews with us, made suggestions, voted, and reported bugs!

  Last modified on Oct 14, 2025

  Was this helpful?
  Yes
  No
  Provide feedback about this article

  Original source Report a problem

  Show more
• Oct 7, 2025

  • Parsed from source:
    Oct 7, 2025
  • Detected by Releasebot:
    Oct 8, 2025
  

  Confluence by Atlassian

  Confluence 10.1.0

  Confluence 10.1.0 lands as a focused bug‑fix release, delivering stability and performance improvements, upgrade guidance, and several fixes across reindexing, calendars, login prompts, and editor quirks. A smoother, more reliable daily experience for teams using Confluence.

  Confluence 10.1.0 Release Notes

  The Atlassian Confluence team is pleased to announce the release of Confluence 10.1.0, which is a bug-fix release.

  Don't have Confluence 10.1 yet?

  Check out the new features and other highlights in the Confluence 10.1 release notes.

  Get the latest version.

  We recommend you read the Confluence 10.1 upgrade notes and you back up your confluence-home directory and database before upgrading.

  Issues resolved in 10.1.0 include various bugs and suggestions such as:

  • API endpoint to trigger reindexing (CONFSERVER-44340)
  • Table column values do not appear on a page following a Confluence upgrade (CONFSERVER-100830)
  • Confluence upgrade via windows installer not working [9.2.7 - 10.0.2] (CONFSERVER-100750)
  • Confluence Team Calendar Can't Pull Jira Cloud Projects Data (CONFSERVER-100548)
  • Cursor jumps to the top when clicking far right on large pages (CONFSERVER-100547)
  • Users are regularly prompted for authentication in Outlook and Apple Calendars in Confluence 9.2+ (CONFSERVER-100021)
  • Confluence can encounter OOM issue intermittently due to Hibernate L2 cache (CONFSERVER-99864)
  • KB articles asking for login to Confluence when JSM customer/user tries to view on Confluence (CONFSERVER-100066)
  • Session validation for Crowd SSO1 continue indefinitely after receiving HTTP 404 (CONFSERVER-100545)
  • Space Attachments macro pagination is not working as expected (CONFSERVER-100357)
  • Create from Template Macro with Variables Overwrites Existing Pages (CONFSERVER-100325)
  • Microsoft Entra ID Group Filtering only filters the last group in the list (CONFSERVER-99079)
  • Undo button does not work for hyperlinks when Synchrony is disabled (CONFSERVER-100800)
  • RegEx Search Not Functioning in Source Code Editor (CONFSERVER-100799)
  • Images in page layout containers configured as "Original" cannot fit the container if the container gets small enough (CONFSERVER-100762)
  • Long usernames in page restrictions dialogue cause accessibility issues (CONFSERVER-100760)
  • Anchor links to unicode emoji headings do not redirect correctly (CONFSERVER-100743)
  • S/Notify Email encryption fails in Confluence 10.0 due to jakarta.mail Incompatibility (CONFSERVER-100595)
  • Undo and Redo buttons appear active even after discarding the draft page (CONFSERVER-100593)
  • Cursor is placed at the start of a newly inserted hyperlink instead of the end (CONFSERVER-100546)

  Showing 20 out of 44 issues fixed in this release.

  Last modified on Oct 7, 2025.

  Original source Report a problem

  Show more
• Oct 6, 2025

  • Parsed from source:
    Oct 6, 2025
  • Detected by Releasebot:
    Oct 8, 2025
  • Modified by Releasebot:
    Oct 26, 2025
  

  Confluence by Atlassian

  Confluence 9.2.9

  Confluence 9.2.9 delivers a bug fix sweep, addressing page data after upgrades, SSO session hangs, and editor and integration issues. Patches Word attachments, RegEx search, non Latin chars, and calendar sync for a smoother experience.

  Confluence 9.2.9 release notes

  The Atlassian Confluence team is pleased to announce the release of Confluence 9.2.9, which is a bug-fix release.

  Don't have Confluence 9.2 yet?

  Check out the new features and other highlights in the Confluence 9.2 release notes.

  Get the latest version

  We recommend you read the Confluence 9.2 upgrade notes and you back up your confluence-home directory and database before upgrading.

  Issues resolved in 9.2.9 include:

  • CONFSERVER-100830: Table column values do not appear on a page following a Confluence upgrade (Bug, Highest priority, Fixed)
  • CONFSERVER-100545: Session validation for Crowd SSO1 continue indefinitely after receiving HTTP 404 (Bug, Medium priority, Fixed)
  • CONFSERVER-99079: Microsoft Entra ID Group Filtering only filters the last group in the list (Bug, Medium priority, Fixed)
  • CONFSERVER-100799: RegEx Search Not Functioning in Source Code Editor (Bug, Low priority, Fixed)
  • CONFSERVER-100544: Office Word Macro not listing Attachments from Page (Bug, Low priority, Fixed)
  • CONFSERVER-100538: Velocity allowlist error for org.apache.commons.lang3.StringUtils (Bug, Low priority, Fixed)
  • CONFSERVER-99832: Not able to edit a file containing non-Latin and umlaut characters using the Office Connector macro (Bug, Low priority, Fixed)
  • CONFSERVER-91450: Subscribing to third party calendars with username + password causes a 500 Error (Bug, Low priority, Fixed)

  Last modified on Oct 7, 2025.

  Original source Report a problem

  Show more
• Oct 1, 2025

  • Parsed from source:
    Oct 1, 2025
  • Detected by Releasebot:
    Oct 19, 2025
  

  Confluence by Atlassian

  Confluence 10.1

  • Find and sort most used macros in your site
  • Manage your integrations and automations with service accounts
  • Connect securely with OAuth 2.0 for app links
  • Upgrade to React 18.3 and latest Atlaskit
  • Editor upgrade to TinyMCE 7.9.1

  Original source Report a problem
• October 2025

  • No date parsed from source.
  • Detected by Releasebot:
    Oct 19, 2025
  

  Confluence by Atlassian

  Confluence Data Center 10.1

  Confluence 10.1 brings key upgrades including OAuth 2.0 for app links, React 18.3, Atlaskit, and TinyMCE 7.9.1, with consolidated release and upgrade notes. The guide covers LTS options, platform changes, and a clear upgrade path from older versions.

  Need help deciding which version of Confluence is best for your team? Use this matrix to compare version features, critical bug fixes, supported platforms, and technical upgrade procedures. We've also outlined specific upgrade paths to make your upgrade as seamless as possible.

  Ready to upgrade? Head to Upgrading Confluence for a step-by-step guide.

  About Long Term Support releases

  A Long Term Support (LTS) release is a feature release that gets backported critical security updates and critical bug fixes during its entire two-year support window. If you can only upgrade once a year, consider upgrading to an LTS release.
  Explore LTS releases

  Top features

  • 10.1
    • Find and sort most used macros in your site
    • Manage your integrations and automations with service accounts
    • Connect securely with OAuth 2.0 for app links
    • Upgrade to React 18.3 and latest Atlaskit
    • Editor upgrade to TinyMCE 7.9.1

  Critical bug fixes

  • 10.1
    • Showing 20 out of 45 issues
    • All 10.1.x bug fixes

  Supported platforms changes

  • 10.1
    • No changes

  Technical upgrade notes

  • 10.1
    • Starting with Confluence Data Center 10.1, we've combined the upgrade notes and release notes into a single page.
    • Confluence 10.1 Release notes List of release notes for all Confluence versions

  Upgrade path

  Upgrading from 6.0 or later

  You can upgrade to any 8.x version at any time! Check the upgrade notes above to make sure everything is compatible, and you're prepared for the transition.

  Use the table below to determine the most efficient upgrade path from your current version to the latest versions of Confluence.

  Recommended upgrade path to Confluence 10

  • 2.7 or earlier
    • Upgrade to 2.7.4 then upgrade to 3.5.17, and follow the paths below.
  • 2.8 to 3.4
    • Upgrade to 3.5.17, and follow the paths below.
  • 3.5
    • Upgrade to 5.0.3, and follow the paths below.
  • 4.0 to 4.3
    • Upgrade to 5.10.x, and follow the paths below.
  • 5.0 to 7.11
    • Upgrade to 7.19.x, and follow paths below.
  • 7.12.x to 10.x
    • Upgrade directly to the latest version of Confluence 10.

  Before you begin, it's critical that you follow all of the steps in Upgrading Confluence. Confluence 8.x is a major upgrade, so it is important that you take a full backup, and test your upgrade in a non-production environment before upgrading your production site.

  Post upgrade checklist

  • Once you have completed the steps required to upgrade your Confluence installation, check all the items on the Confluence post-upgrade checklist to ensure that everything works as expected. If something is not working correctly, check for known Confluence issues in the Upgrade Notes and try troubleshooting your upgrade as described.

  Original source Report a problem

  Show more
• Sep 29, 2025

  • Parsed from source:
    Sep 29, 2025
  • Detected by Releasebot:
    Oct 19, 2025
  

  Confluence by Atlassian

  Confluence 10.1 upgrade notes

  Upgrade notes are now included in the release notes

  Starting with Confluence Data Center 10.1, we've combined the upgrade notes and release notes into a single page. You’ll find all improvements and changes in one place, so there’s no need to switch between pages.

  Explore the Confluence 10.1 release notes

  Original source Report a problem
• Sep 24, 2025

  • Parsed from source:
    Sep 24, 2025
  • Detected by Releasebot:
    Sep 29, 2025
  

  Jira by Atlassian

  Jira Software 11.1.x upgrade notes

  Upgrade notes are now included in the release notes

  Starting with Jira Data Center 11.1, we've combined the upgrade notes and release notes into a single page. You’ll find all improvements and changes in one place, so there’s no need to switch between pages.

  Explore the Jira Software 11.1 release notes

  Last modified on Sep 24, 2025

  Original source Report a problem