Atlassian Release Notes
291 release notes curated from 305 sources by the Releasebot Team. Last updated: Nov 13, 2026
Atlassian Products
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
[Announcement] New Ecoscanner Security Checks Coming Soon for Marketplace Forge Apps
Bitbucket expands Ecoscanner with automated security checks for Marketplace Forge apps, covering code execution, outdated Node.js runtimes, token use, exposed secrets, SQL injection, and TLS settings. Checks will roll out periodically before the end of 2026, with extra remediation time for some findings during launch.
What’s Changing
We're expanding Ecoscanner with new automated security checks for Marketplace Forge apps to ensure compliance with our Security Requirements for Cloud Apps. These checks will be released periodically before December 31, 2026.
The new checks include:
- Arbitrary code execution: Detects untrusted input reaching dynamic code execution (e.g., eval) in Forge functions (Requirement 8, Critical Severity).
- End-of-life Node.js runtimes: Flags apps using Node.js runtimes that have reached end-of-life (Requirement 10, Critical Severity).
- Atlassian API token usage: Detects apps authenticating to Atlassian APIs using user API tokens instead of app-based authentication (Requirement 11, Critical Severity).
- Secrets in logs: Detects sensitive data (e.g., credentials) written to application logs via console.log or similar (Requirement 5, High Severity).
- SQL injection: Detects user input interpolated directly into Forge SQL queries instead of using query parameters (Requirement 8, High Severity).
- TLS and HSTS on Forge remotes: Verifies that remote backends accept only TLS 1.2+ and return an HSTS header with a max-age of at least one year (Requirement 3, Medium Severity).
What You Need to Do
As these scanners go live, findings will be reported to you via AMS tickets in ecosystem.atlassian.net.
To account for the holiday period, we are providing an additional 30 days beyond the standard Security Bug Fix Policy for findings from High or Medium severity checks during this initial launch. Standard resolution timeframes will apply to all findings starting January 1, 2027.
More details on how these checks work will be included in the Ecoscanner documentation as they are released. If you have questions, please contact Developer Support.
Original source - Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 13, 2026
Scaling Jira to ~6M Versions
Jira Search improves JQL performance at scale by resolving version lookups within projects and splitting large unscoped queries into parallel batches, cutting P99 resolution time from 18 seconds to 92 milliseconds.
Jira Search has to keep up as our customers’ data grows. Our largest customers tracks millions of releases, and for us that meant supporting nearly 6 million software release versions. At that scale, even preparing a search query became a bottleneck. It relied on loading versions into memory and filtering them there, which stopped being viable at our largest customers’ scale. We changed how we retrieve and process that data, and P99 query resolution time dropped from around 18 seconds to 92 milliseconds. This post covers how we found the bottleneck and fixed it.
How Jira Turns JQL into Search Results
Jira lets you create work items (previously called issues), and some customers create tens of millions of them. To show charts, boards and filters, we need to search through these work items. Jira Search is the service that makes this possible, giving one consistent way to search across every work item a customer has.
Jira Search lets users write JQL (Jira Query Language) to get a customized list of work items. Many internal experiences, and more broadly any experience powered by work items, also use JQL under the hood to fetch the work items they show. JQL looks a lot like SQL, and both serve the same purpose, which is search.
You define the search query in JQL, and the matching work items are fetched from the datastore. For example, take this query.
project = "Test" and assignee = currentUser()This query fetches all work items assigned to the currently logged-in user. A JQL query is made up of smaller parts called clauses. The query above contains a project clause and an assignee clause, and uses the JQL function currentUser().
Before the search engine runs a query, it first resolves it. Every name and function in the query is replaced with the exact id it refers to, so the query is ready to execute against the datastore. For example, the query above becomes something like this.
project = "test-id" and assignee = "current-user-id"Where Versions Enter the Query
Besides assignee and project, a Jira work item has many more fields. One of them is version, which teams use to track releases. Most fields are cheap to resolve because the query names one exact value, like a single user or a single project, but versions work differently.
The simplest way to search by version is to name it directly.
project = "Test" and fixVersion = "v1"JQL also has functions that pick versions for you, such as earliestUnreleasedVersion() and latestReleasedVersion(). Like currentUser() in the assignee example, the search engine has to resolve these into ids before it can run the query.
project = "Test" and fixVersion = earliestUnreleasedVersion()To resolve this, the search engine has to find the earliest unreleased version and replace the function with its id. That sounds simple, but it means looking at millions of versions, checking which ones are unreleased, and working out which comes first. This step became our bottleneck.
When Loading Everything Worked
When version functions were first implemented, resolution relied on in-memory filtering to keep it fast. Since customers had a fairly limited number of versions, all of them were fetched and kept in application memory for further processing.
At that scale, this was a well-balanced solution. It gave us
- Fast in-memory filtering
- No extra network calls once the versions were loaded
Millions of Versions Changed the Equation
As the number of versions grew, loading all of them on every lookup started to hurt in two ways.
- Database scans. Reading millions of rows was slow. We added a cache in front of the database, which bought us time but did not fix the underlying problem.
- Network latency. Even with the cache, a single lookup could pull hundreds of thousands of rows across the network. That transfer alone added seconds to affected queries.
Without a project in the query, the function has to return the earliest unreleased version for every project, so for a large customer a single call could expand into a list of 100k+ version ids before the query even reached the datastore. For a customer with ~6M versions, the slowest resolutions took almost 30 seconds, and even the P99 resolution time was around 18 seconds.
To fix this, we needed a way to resolve version functions efficiently.
Resolve Only What the Project Needs
We started by looking for patterns in the queries being executed. We found that in more than 80% of cases, the version function is accompanied by a project clause. A customer can have a huge number of versions in total, but a single project has relatively few. If a customer has 100k versions but a project has only 2, a project-scoped search only needs to look at those 2. That means far less data crosses the network, and the database lookup itself is much faster because it can filter by project.
To take advantage of this pattern, we changed how JQL is resolved and split queries into two kinds, based on whether the query includes a project or not.
- Project-scoped queries, e.g. project = MERA and fixVersion = earliestUnreleasedVersion()
- Project-unscoped queries, e.g. fixVersion > 4.0
Internally, a resolved query is represented as a tree, which makes it easy to spot project-scoped queries.
Resolution now detects project-scoped queries and uses that project when resolving version functions. Previously, a query was resolved like this.
project = "234" and fixVersion in ("123", "456", ... 100k+ more)Now the same query resolves like this.
project = "234" and fixVersion in ("567")Project scoping meant scanning a few hundred rows instead of a few million, eliminating the large allocations that had caused instances to run out of memory. Assuming 500 bytes per loaded version, this reduces the version-data memory consumption from about 3 GB for ~6M versions to 250 KB for ~500 versions.
Project scoping reduced P99 resolution time from ~18 seconds to 92 milliseconds, an approximately 196× speedup.
No Project Filter? Split the Lookup
Project-unscoped queries were still a problem. Without a project to narrow the lookup, database latency on the largest datasets could push resolution past our timeout budget. To improve this, we implemented a solution based on chunking.
As the number of version ids included in the final database query grew very large, the Postgres query planner stopped using the index. Postgres picks the plan it estimates to be cheapest, and with tens of thousands of ids in the IN list it expected a large share of the table to match. At that point, reading the whole table linearly looked cheaper than looking up each id through the index, so it fell back to a sequential scan even though we were passing an exact set of ids. Planning a query with such a long list was also expensive on its own. This took away the benefit we should have had, since version_id is the primary key and therefore indexed.
Another option is to pass the IDs as a PostgreSQL array and use ANY or an UNNEST subquery. This keeps the SQL compact and could avoid the additional round trips and application coordination required by chunking. However, it does not guarantee indexed lookups; PostgreSQL still selects a plan based on estimated costs. Our scale tests validated chunking for this workload, reducing SQL fetch times from over 30 seconds to under 700 milliseconds. Establishing whether an array-based query performs better would require a direct comparison using representative data and concurrency.
We replaced the single large fetch with smaller chunked requests that run in parallel and together return the full set of versions. Choosing the batch size was a trade-off. Batches that are too large push Postgres back to a full table scan, and batches that are too small create too many parallel calls. We picked the largest batch size that still keeps Postgres on the version_id index.
What We Learned and What’s Next
Our changes brought P99 resolution time for project-scoped queries down from 18 seconds to 92 milliseconds. For unscoped queries, SQL fetch times dropped from over 30 seconds to under 700 milliseconds. That gave us room to grow without larger architectural changes.
The fixes themselves were specific to versions, but the problem behind them is quite common. Customers use the same product in very different ways. One might have a few hundred versions, and another has millions. A design that is fast for nearly everyone can still break down at the far end, and averages won’t show it. You only see it in the long tail.
Fixing that kind of problem rarely comes down to one clever idea. It took real usage data to realise that most queries named a project, and a close look at how Postgres plans queries to understand why a long list of ids made things slower instead of faster. Neither fix was obvious from the code alone. Both came from studying how the data was actually shaped and queried. And as customers keep growing, that work never really ends. Queries that are fine today will need another look tomorrow, which is why we keep instrumenting the long tail rather than waiting for it to surface
Which is why we are also continuing to scale Jira Search beyond these fixes. With JSIS (Jira Scalable Issue Search), we’re moving JQL search out of the Jira database and onto a dedicated search engine built on OpenSearch. As part of that work, we plan to index version data there too, so versions sit right next to the work items that use them.
Original source All of your release notes in one feed
Join Releasebot and get updates from Atlassian and hundreds of other software products.
- Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
[Added] New Bitbucket Custom Deployment check module
Bitbucket adds the bitbucket:deploymentCheck module, enabling developers to build custom deployment checks for Bitbucket Cloud.
Registering the new bitbucket:deploymentCheck module. You can use this module to build custom deployment checks for Bitbucket Cloud. The motivation for this change is laid out here, with the aim to create a centralised checks platform. Some more details on future strategy and vision is mentioned in this doc.
Original source - Nov 3, 2026
- Date parsed from source:Nov 3, 2026
- First seen by Releasebot:Nov 4, 2026
Issues resolved in 11.0.1
Confluence releases version 11.0.1, a bug-fix update that improves Kubernetes token reloading, PDF exports, mail archives, notification handling, and trash cleanup.
The Atlassian Confluence team is pleased to announce the release of Confluence 11.0.1, which is a bug-fix release.
Don't have Confluence 11.0 yet?
Check out the new features and other highlights in the Confluence 11.0 release notes.
Get the latest version
We recommend you read the Confluence 11.0 release notes and you back up your confluence-home directory and database before upgrading.
Released on 03 November 2026
Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-104494 Confluence DC does not reload rotated Kubernetes projected service-account tokens Bug Oct 09, 2026 14:08 Nov 03, 2026 08:37 Edward Tejaswini P Medium CLOSED Fixed CONFSERVER-95936 PDF space export changes the page title when special characters like <>& are present in the page title Bug Jun 06, 2024 08:26 Nov 03, 2026 08:37 Pille Saral Juwin Zam Medium CLOSED Fixed CONFSERVER-87537 OutOfMemoryError caused by non-delivered mails/notifications accumulated in the ErrorQueue Bug Jun 08, 2023 11:35 Nov 03, 2026 08:37 Abhiraj Saxena Iker Alonso Medium CLOSED Fixed CONFSERVER-104497 Opening an archived mail in a space's Mail Archive fails with HTTP 500 "System Error" when the space has a mail account configured Bug Oct 14, 2026 10:26 Nov 03, 2026 08:37 agawron Shruthi Hebbal Low CLOSED Fixed CONFSERVER-76019 Purge All trash with custom content will run forever and never finish. Bug Jan 13, 2022 06:41 Nov 03, 2026 08:37 Tom Smallridge Quan Pham Low CLOSED Fixed Original source - Nov 3, 2026
- Date parsed from source:Nov 3, 2026
- First seen by Releasebot:Nov 4, 2026
Issues resolved in 10.2.20
Confluence releases version 10.2.20 with bug fixes for Kubernetes token reloading, accessibility, PDF exports, notification queues, archived mail errors, and trash cleanup, improving reliability for Confluence Data Center users.
The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.20, which is a bug-fix release.
Don't have Confluence 10.2 yet?
Check out the new features and other highlights in the Confluence 10.2 release notes.
Get the latest version
We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.
Released on 03 November 2026
- CONFSERVER-104494 — Confluence DC does not reload rotated Kubernetes projected service-account tokens
- CONFSERVER-104492 — Keyboard focus indicators are missing for some controls on page view in Confluence 10.2.17+
- CONFSERVER-95936 — PDF space export changes the page title when special characters like <>& are present in the page title
- CONFSERVER-87537 — OutOfMemoryError caused by non-delivered mails/notifications accumulated in the ErrorQueue
- CONFSERVER-104497 — Opening an archived mail in a space's Mail Archive fails with HTTP 500 "System Error" when the space has a mail account configured
- CONFSERVER-76019 — Purge All trash with custom content will run forever and never finish.
6 issues
Original source Similar to Atlassian with recent updates:
- Anthropic release notes965 release notes · Latest Nov 19, 2026
- Notion release notes242 release notes · Latest Nov 16, 2026
- Asana release notes17 release notes · Latest Feb 1, 2026
- Apple release notes169 release notes · Latest Nov 16, 2026
- Canva release notes41 release notes · Latest Jun 24, 2026
- Shopify release notes816 release notes · Latest Nov 18, 2026
- Oct 28, 2026
- Date parsed from source:Oct 28, 2026
- First seen by Releasebot:Nov 11, 2026
[Deprecation Notice] Brownout Notice: SSH access via bitbucket.org is deprecated in favor of ssh.bitbucket.org
Bitbucket is sunsetting SSH access through bitbucket.org in favor of ssh.bitbucket.org to strengthen security. Scheduled brownouts will block traffic to the old hostname and provide error messages and in-product notices to help teams update their usage.
We are sunsetting SSH access via bitbucket.org in favor of ssh.bitbucket.org. This is an important change to improve Bitbucket’s security posture and safeguard our customers from denial of service abuse. We have originally announced this change on May 12, 2026 in Changelog announcement. We will be running a series of brownouts to help teams identify and mitigate any remaining usage of the old hostname.
For the brownout schedule and additional details refer to community blogpost.
During each brownout window, we will:
- Temporarily block SSH traffic on bitbucket.org
- Show clear error messages
- Show in-product messaging to create awareness
- Oct 27, 2026
- Date parsed from source:Oct 27, 2026
- First seen by Releasebot:Oct 27, 2026
Factory brings autonomous coding work into Jira
Jira now lets Cloud customers with Rovo invoke Factory’s Droid coding agent from a work item. Droid uses Jira and Confluence context, runs tasks in a configured environment, streams progress, and writes results back to the issue, with enterprise control over compute and AI models.
Factory and Atlassian have unlocked something big for our shared customers: Factory’s Droid coding agent can now be invoked directly from a Jira work item. Droid picks up the task, runs the engineering work in the selected environment, and writes results back to Jira. It’s the first time teams can hand a Jira issue to a coding agent, use whatever AI model fits their needs, and keep everything running inside their own secure environment.
🎯 The problem
Engineering work starts in Jira, but giving a coding agent the full context and workflow from an issue still takes manual work. Developers re-feed context by hand, run the agent on a separate surface, and the results never make it back to the ticket.
🚀 What’s new
Factory’s Droid coding agent can now be invoked directly from a Jira work item through Rovo Chat. Droid picks up the task, runs the engineering work in the selected environment, and writes results back to Jira — turning the board into the control point for both planning and execution. The integration started with a request from an enterprise customer in a regulated industry that’s building a software factory in a highly controlled environment. That customer brought Factory and Atlassian together, and Factory built the Forge Remote Agent for Jira.
💡 Why it matters
Using AI in development is not the same as orchestrating work with it. Most developers already use AI, but teams still lose time rebuilding context, managing prompts, and reconciling work across tools. Droid in Jira gives teams a direct path from assigned work to autonomous execution while preserving Jira as the system of record. And because Factory is model-independent and deploys across Factory-managed compute, customer infrastructure, and fully air-gapped environments, enterprises keep control over where agents run and which models they use.
⚙️ How it works
From a Jira issue, an engineer invokes Droid in Rovo Chat. On the first run, they configure the Droid — selecting a compute environment, model settings, and service accounts — and those settings can become the default for future tasks. From there, Droid:
- Picks up the Jira work item.
- Pulls relevant Jira and Confluence context through Atlassian MCP.
- Runs the coding task in the configured environment.
- Streams progress into the Jira chat.
- Writes results back to the work item.
The integration runs as a Forge Remote Agent using the A2A protocol.
✅ Availability
The Forge Remote Agent is designed for Jira Cloud customers with Rovo enabled. Each Factory organization links to one Jira site, and Droid is configured on first use.
🔗 Get started
- Atlassian Marketplace listing
- Documentation from Factory on how this app works
- Oct 26, 2026
- Date parsed from source:Oct 26, 2026
- First seen by Releasebot:Nov 11, 2026
[Announcement] Upcoming brownouts and removal of the deprecated Bitbucket Cloud code search API
Bitbucket will begin scheduled Code Search API brownouts in November 2026 ahead of its permanent shutdown, urging integrations to migrate to workspace code search.
Following the previous deprecation announcement, we will begin scheduled brownouts of the Bitbucket Cloud Code Search API on 3 November 2026 at 00:00 UTC.
Brownouts are temporary periods when the API is unavailable, intended to help you identify integrations that still need to migrate. The brownout duration will progressively increase before the API becomes permanently unavailable on 15 November 2026 at 00:00 UTC.
Migrate your integrations to the workspace code search API before the brownouts begin.
Original source - Oct 13, 2026
- Date parsed from source:Oct 13, 2026
- First seen by Releasebot:Oct 13, 2026
[Deprecation Notice] Git Credential Manager (GCM) upgrade required for continued OAuth 2.0 Git authentication
Bitbucket is enforcing rotating OAuth 2.0 refresh tokens, so users of Git Credential Manager with OAuth authentication must upgrade to version 3.0.0 or later by November 30, 2026. Users with personal access tokens or other authentication methods need no action.
What's changing
On 30 Nov 2026 Git requests authenticated using OAuth2.0 via the Git Credential Manager (GCM) will be blocked for versions prior to 3.0.0. This is caused by the lack of support for rotating OAuth refresh tokens, which have recently begun being enforced for Bitbucket’s OAuth 2.0 implementation. See: https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-3052 . Atlassian contributed changes to the open source project to include support for the rotating refresh token model, which was bundled in the v3.0.0 release ( https://github.com/git-ecosystem/git-credential-manager/releases/tag/v3.0.1 )
What you need to do
- If
- Action/s Required?
- You are NOT using Git Credential Manager
- No action is required
- You ARE using Git Credential Manager configured with personal access tokens
- No action is required
- You ARE using Git Credential Manager configured with OAuth2.0
- You must upgrade Git Credential Manager to a version 3.0.0 or higher by 30 Nov 2026 if you wish to continue to authenticate Git using this mechanism. Simply upgrading the version should ensure seamless authentication.
Attached file
Note: Impacted users will see a message after each git push operation prior to upgrade.
Original source - Oct 8, 2026
- Date parsed from source:Oct 8, 2026
- First seen by Releasebot:Oct 24, 2026
Confluence 11.0 release notes
Confluence releases version 11.0 with stronger default security protections, rate limiting, faster indexing, and experimental asynchronous macro execution. The major Data Center update also modernizes its platform and removes legacy features, so administrators and app developers should review upgrade requirements and compatibility changes.
We're excited to present Confluence 11.0
Highlights
- Rate Limiter Settings Enabled By Default
- Rate-limit REST endpoints with annotations
- Confluence Mobile Web Deprecation
- AUI 11
- Asynchronous Macro Execution
- Modernizing and Securing Plugin Data Storage
- Enhanced Security with New Content Security Policy
- Enhanced protection against SSRF
- Custom HTML Editing Now Disabled by Default
- Journal Index Queue Improvements
- Standardize JNDI path validation
- Platform Upgrades for Stability and Resilience
- Logging Modernization to log4j2.xml
- Synchrony logging configuration now uses Log4j 2
- Look and Feel Layouts and Customization Editing Now Disabled by Default
- Restore From Local Drive Now Disabled by Default
- Removal of support for transformed apps
- Sign SAML authentication requests
- V3 Attachment Storage Removal
Further Information
- 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.
Rate Limiter Settings Enabled By Default
For: ADMINS
Confluence 11.0 enables rate limiting by default for automation and application requests. This helps protect Confluence from request bursts that can affect instance stability and availability.
Existing configurations are preserved: If rate limiting is already enabled on your Confluence instance, upgrading to Confluence 11.0 does not change your existing rate-limiting mode or configured limits.
After upgrading, review your rate-limiting configuration in the administration interface. The default limits are intended to suit typical instances, but you can adjust or disable them to match your traffic patterns and integration requirements.
Important for administrators: If you use high-volume automation or integrations, validate their request rates after upgrading and tune the configured limits as needed.
Rate-limit REST endpoints with annotations
For: ADMINS
We've added the ability to rate limit individual REST API endpoints, so a single script, automation, or integration can no longer degrade your instance by hammering one expensive endpoint. Limits apply per user, per node, and requests that exceed them receive an HTTP 429 response with a Retry-After header telling the user when to try again.
As an administrator you can tune or switch off any of these limits using JVM system properties in the com.atlassian.ratelimiting.api.* namespace, without waiting for an app update. This complements the existing rate limiting in your admin settings, which caps a user's total traffic rather than their use of a specific endpoint.
Confluence Mobile Web Deprecation
For: ADMINS
We have disabled the legacy Confluence mobile web interface in Confluence 11.0. This change does not affect the Confluence Data Center mobile app.
When users access Confluence from a mobile browser, Confluence now prompts them to either:
- download the Confluence Data Center mobile app, or
- continue to the desktop version of Confluence in their browser.
Existing links to the former mobile interface redirect to the corresponding standard Confluence page where possible.
AUI 11
For: ADMINS
We’re introducing AUI 11 with the next major versions of our Data Center products, bringing a refreshed visual experience that aligns more closely with Atlassian Cloud. The update includes refreshed badges, banners, and application headers, a modernised icon set, and updated typography using Atlassian fonts and design system themes.
If you use Marketplace apps or custom in-house apps with a frontend, ensure they’re compatible with the new major version before upgrading.
Asynchronous Macro Execution
For: ADMINS EXPERIMENTAL
Confluence Data Center now supports asynchronous macro execution — a major performance capability that changes how macros are rendered on a page.
Previously, every macro on a Confluence page was executed sequentially on the same HTTP request thread. The browser couldn't receive the page until every last macro had finished — meaning a single slow macro (e.g. a Jira query or a blog-posts roll-up) could block an entire page load for all users.
With this release, macros can be configured to execute asynchronously and concurrently in a dedicated thread pool. The HTTP request thread is freed immediately, and macro results are assembled as they complete. For pages with multiple slow macros, this can dramatically reduce perceived load time.
Configuration required: Yes (opt-in per macro, admin setup)
Concurrent execution
Multiple macros on the same page can now execute in parallel rather than sequentially, significantly reducing total page render time.
Deduplication
If multiple users request the same page simultaneously, identical macro executions (same macro, same parameters, same content) can be deduplicated — one execution runs and its result is shared, avoiding redundant parallel work.
Configurable timeouts and rate limits
Administrators can set per-macro time limits and concurrency limits via the REST API, with global defaults configurable via JVM system properties. If a macro exceeds its time limit, Confluence can signal it to stop gracefully.
Result caching (opt-in)
Macro results can be cached per-user on each node, so repeat visits to the same page don't re-execute expensive macros. Cache TTL and size are configurable.
Execution cancellation
Administrators can cancel in-flight macro executions in real time — by execution ID, by macro name, or all at once — via REST API. Macro developers can implement graceful cancellation support.
Observability
Active macro executions are visible in real time, both via REST API and (on clustered setups) in the Confluence Clustering UI. A scheduled analytics job publishes execution statistics for monitoring.
Safe fallback
If the async thread pool is saturated (queue full or queue latency exceeded), macros fall back to synchronous execution automatically. No requests are dropped.
How to get started
This feature is disabled by default and requires administrator configuration:
- Enable the dark feature atlassian.macros.async.execution in Confluence Dark Features
- Use the REST API (PUT /rest/asyncmacros/latest/execution-controls) to configure which macros run asynchronously
- Optionally tune thread pool and timeout settings via JVM system properties
Modernizing and Securing Plugin Data Storage
For: ADMINS
Removal of legacy structures for storing plugin data will secure Confluence for long term stability. After making these legacy systems read-only in Confluence 10.0, we have removed them entirely in Confluence 11.0. This includes the Removal of Bandana, and the removal of OpenSymphony PropertySet (osProperty). For security reasons, Confluence 11.0 will also no longer bundle the XStream library.
Direct access to the Bandana database table and OpenSymphony PropertySet will no longer be possible in Confluence 11.0. Please ensure all Apps that currently use Bandana are migrated to alternative storage (for example, Active Objects or SAL Plugin Settings) before upgrading to Confluence 11.
To make this feasible, upgrade to Confluence 11.0 will be supported only from the latest Confluence 10.2.x release (that is, customers must upgrade to the latest 10.2.13+ before upgrading to 11.0).
Migrating data will no longer be possible in Confluence 11.0 - you must complete migration before you upgrade.
For migration guidance, refer to Preparing for Confluence 10.0 for more information.
The BANDANA table is deprecated and will be removed automatically in a future release. You can drop it now by setting -Dconfluence.enable-drop-bandana-table=true before the upgrade. Back up the table before doing so if you want to retain the data.
Enhanced Security with New Content Security Policy
For: ADMINS
In Confluence 11, the content security policy (CSP) for the "script-src" directive has been introduced. The following adjustments apply:
- All direct and indirect uses of eval are blocked.
- All inline scripts are blocked.
- Scripts loaded from other domains must be allowed via the CSP script-src header.
- Script tags with inline code must include a nonce attribute.
- Keyboard shortcuts with operation type execute are no longer supported.
How is script-src CSP enabled
Confluence 11 enables this by default alongside existing policies. Only system administrators can disable this feature via the configuring of system properties:
http.header.security.content.security.policy.strictness.enabled
(e.g. -Dhttp.header.security.content.security.policy.strictness.enabled=false)
The CSP report-only mode is disabled when the property CSP is enabled (set to true).
There is also a system property http.header.security.content.security.scriptsrc.additional.urls that let admins to allow external scripts if they are needed.
Enhanced protection against SSRF
For: ADMINS
We’re introducing two security enhancements for Confluence, Jira Software, and Jira Service Management Data Center to strengthen protection against Server-Side Request Forgery (SSRF) attacks. These changes help block unauthorized outbound requests to sensitive destinations, ensuring your instance remains secure.
Key changes include:
- New default outbound denylist: We’ve added a built-in denylist that automatically blocks requests to dangerous destinations, such as cloud metadata services (AWS, Google Cloud, Azure), private networks, and insecure protocols (for example, file:// and shell://).
- Extended allowlist enforcement: Several platform components that previously bypassed the allowlist, including OAuth2, Gadgets, Webhooks, and the Universal Plugin Manager (UPM), now strictly follow your allowlist configuration.
- DNS resolution checking: The denylist now resolves domain names to their IP addresses to prevent bypass attempts via DNS rebinding.
These protections are enabled by default. They provide immediate security against SSRF attacks without requiring extra configuration. While you can disable the denylist using the -Dssrf.denylist.enabled=false JVM system property, we don’t recommend this for production environments.
While a denylist blocks known-dangerous destinations, we recommend configuring a comprehensive allowlist. An allowlist is the most effective defense against SSRF because it limits outbound requests only to the specific, trusted destinations your instance needs to function.
Custom HTML Editing Now Disabled by Default
For: ADMINS
To improve security, editing custom HTML is now disabled by default. If you need to enable custom HTML, set the confluence.custom.html.config.enabled system property to true. Only system administrators can enable this feature. How to configure system properties
Journal Index Queue Improvements
For: ADMINS
The content index queue is now processed fairly across content types instead of strictly in queue order. Entries are grouped by content type (pages and blogs, attachments, comments, user profiles, custom content, other). As a result, A bulk operation on one content type — a mass attachment upload, a space import — can no longer delay indexing of everything queued behind it. Queue depth per content type is shown on the Content indexing admin page.
This change applies to the content index journal (main_index) only; other journals keep the linear path.
To turn off the fair Index queue, disable the confluence.fair.journal.index.queue dark feature.
Concurrent Processing
Due to the grouping of entries we can now process the entries in batches concurrently, increasing performance. A number of worker threads are made from the CPUs available to the JVM (capped at 50) and the index queue gives each worker at least 100 entries each to process.
To fall back to serial processing, disable the confluence.fair.journal.index.queue.parallel.processing dark feature — no restart is needed.
Standardize JNDI path validation
For: ADMINS
We’re standardizing how our products validate and use Java Naming and Directory Interface (JNDI) paths. Inconsistent checks across different products can sometimes allow crafted inputs to trigger unintended code execution. By unifying these validation processes, we're reducing the risk that a misconfiguration or an overlooked pathway could become a security entry point.
This change helps protect your data and ensures service reliability by aligning all products on a single, safe approach to JNDI lookups.
Platform Upgrades for Stability and Resilience
For: ADMINS
We have been busy at work upgrading the Confluence 11 platform to set Confluence up for success in the long term. In most cases these changes are transparent. However, if you use Marketplace apps or custom in-house apps, ensure they are compatible with the new major version before upgrading. Some of the more notable changes can be seen below.
Update to jQuery 4
We’re upgrading to jQuery 4 to align on jQuery versions across all Data Center products. This means a significant jQuery version uplift for products containing older versions of jQuery.
Java 25 is now the minimum supported version
Starting from Confluence 11, Java 25 is the minimum supported version for both compile and runtime environments. At the same time, all components run on JDK 25.
Upgrade to React 19
We're upgrading to React 19 across all Data Center products to keep our frontend dependencies secure and compliant. This change ensures we can continue upgrading other critical frontend libraries in the future.
Modernize your outgoing network connections (HttpClient 5)
We're modernizing how our products make outgoing network connections by removing an older networking component that's no longer actively maintained: Apache HttpClient 4. This change reduces long-term security and reliability risks and ensures our technology remains supported and aligned with current standards.
Jakarta 11 and Spring 7 upgrade
We’re updating our Jakarta and Spring dependencies to continue meeting your demands for secure and compliant products. This change ensures we stay aligned with security policies and receive the latest updates.
Upgrade to Jackson 3
We’ve upgraded the Jackson library to ensure your instance and apps are secure, compliant, and compatible with the latest industry standards.
For most customers, this change won't affect how you use your apps. However, if you use or develop extensions, take note of the following:
- We've notified Marketplace partners of this change. They're responsible for updating their apps to ensure continued compatibility.
- If you've developed custom, in-house apps or integrations, your development team must update the Jackson 2 libraries to version 3 in your codebase.
Logging Modernization to log4j2.xml
For: ADMINS
From Confluence 11.0, Log4j 1 configuration and API have been removed for security and modernization. As a result of this, the log4j.properties format will no longer be used and is replaced by log4j2.xml. Below are the affected files:
Up to 10.2.x
- /confluence/WEB-INF/classes/log4j.properties
- /confluence/WEB-INF/classes/log4j-diagnostic.properties
From Confluence 11.0
- /confluence/WEB-INF/classes/log4j2.xml
- /confluence/WEB-INF/classes/log4j2-diagnostic.xml
Any log4j.properties left in place after an upgrade is ignored, not merged. Confluence logs a warning at startup if it finds these log4j property files. If you customised logging, re-apply those changes to log4j2.xml when upgrading, then delete log4j.properties to silence the warning. Setting log levels at runtime through Logging and Profiling in the admin UI is unchanged.
Synchrony logging configuration now uses Log4j 2
For: ADMINS
Synchrony 7.0.13 (bundled in Confluence 11.0) no longer supports Log4j 1 configuration files or the legacy log4j.configuration system property.
- If you do not use a custom Synchrony logging configuration, no action is required. Synchrony uses its bundled Log4j 2 configuration by default.
- If you currently use a custom synchrony-log4j.properties file, convert it to a Log4j 2 XML configuration file and configure it using log4j2.configurationFile.
Confluence-managed Synchrony
Create a Log4j 2 XML configuration file, then add the following to your synchrony-args.properties file:
log4j2.configurationFile=file:///absolute/path/to/synchrony-log4j2.xmlStandalone Synchrony
Create a Log4j 2 XML configuration file, then add the following to OPTIONAL_OVERRIDES in your start-synchrony.sh or start-synchrony.bat script:
OPTIONAL_OVERRIDES="-Dlog4j2.configurationFile=file:///absolute/path/to/synchrony-log4j2.xml"Log4j 1 .properties files are not automatically converted or merged with Log4j 2 configuration.
Look and Feel Layouts and Customization Editing Now Disabled by Default
For: ADMINS
To improve security, configuring Look and Feel customization is now disabled by default. Admins can only view existing layout configurations. To enable look and feel customization, set the confluence.custom.look.and.feel.enabled system property to true. Only system administrators can enable this feature.
- Look and Feel customization will be disabled by default at both Global and Space level. Setting the system property to true will enable customization at both the places.
- In addition to this, for Space level stylesheet configuration ensure that “Custom Stylesheets for Spaces” is enabled in Security Configuration.
How to configure system properties
Restore From Local Drive Now Disabled by Default
For: ADMINS
To improve application security, restoring of data from local drives is now disabled by default. To enable restoring of data from local drive , set confluence.restore.from.local.drive.enabled system property to true. Only system administrators can enable this feature via the configuring of system properties.
Removal of support for transformed apps
For: ADMINS
We’re removing support for the transformed app format to improve the performance and reliability of Data Center products. Starting with this release, the Universal Plugin Manager (UPM) will no longer install or enable apps using this older format, and we’ve removed the infrastructure that converted these formats at startup. This change helps your instance start faster and reduces the risk of stability issues.
Before you upgrade, ensure your Marketplace apps are compatible with <product name+version>. If you use custom in-house apps, you must migrate them to the transformerless format. The following guides might help you in this process:
- How to automate the migration process
- More about identifying and converting plugins
Sign SAML authentication requests
For: ADMINS
We’re implementing signed Security Assertion Markup Language (SAML) authentication requests to strengthen your instance’s security. When SAML is enabled, the authentication plugin generates a certificate and private key during startup. The private key signs SAML authentication requests, and you can download the certificate to upload to your Identity Provider (IdP). This lets the IdP verify the authenticity and integrity of each request.
To enable signing SAML authentication requests, go to the Authentication methods page and select Sign requests. Explore SAML single sign-on for Atlassian Data Center applications
V3 Attachment Storage Removal
For: ADMINS
Confluence 8.1 introduced the v4 attachment layout and a background migration that moved attachment data from ver003 to v4. Confluence 11.0 removes version 3 (ver003) attachment storage entirely: the storage implementation, the automatic V3 → V4 migration, and the related APIs.
Note that the V3 → V4 migration no longer runs in Confluence 11.0 and must have been completed prior to upgrading
Supported platforms changes
This section contains a run-down of all the changes that have been made to supported platforms since the last Confluence LTS release. See the complete list of supported platforms
We’ve confirmed support for:
- JDK 25
- MySQL 8.4
- Oracle AI Database 26ai (rebranded from Oracle 23ai)
- PostgreSQL 17
- OpenSearch 2.11 through to 12.19
This version of Confluence runs only on Java 25.
End of support announcements
We've removed support for:
- PostgreSQL 16
- Aurora PostgreSQL 16
- MS SQL Server 2019
- Oracle 19c
- Java 21
We’ve deprecated support for:
- MySQL 8.4
- MS SQL Server 2022
For more information on these notices, see End of Support Announcements for Confluence.
App developers
Head to Preparing for Confluence 11.0 to find out more about changes under the hood. These include but are not limited to:
- Jsoup Upgrade
- Frontend AMD and WRM Resources Removal
- JQuery plugins removal
- Removing Bundled Joda time
- Atlassian Keyboard Shortcuts Upgrade
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
You must first upgrade to the latest Confluence 10.2 release first before upgrading to Confluence 11.0.
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 10.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 11.0.0
Released on 08 October 2026
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!
Original source - Oct 5, 2026
- Date parsed from source:Oct 5, 2026
- First seen by Releasebot:Oct 25, 2026
Issues resolved in 11.3.12
Jira releases Software 11.3.12 with fixes for performance, indexing, and usability issues, alongside published security updates for denial-of-service and arbitrary file access vulnerabilities in Jira Data Center.
The Atlassian Jira team is pleased to announce the release of Jira Software 11.3.12.
Don't have Jira Software 11.3.x yet?
Check out the new features and other highlights in the Jira Software 11.3.x release notes.
Get the latest version
Released on 5 October 2026
T | Key | Summary | Status | Security Level
- Public Security Vulnerability | JSWSERVER-27017 | DoS (Denial of Service) org.jsoup:jsoup Dependency in Jira Software Data Center | PUBLISHED
- Bug | JSWSERVER-26931 | The sub-tasks are displayed under Sub-tasks panel and under Child issues panel | CLOSED
- Bug | JSWSERVER-26929 | Refreshing an Advanced Roadmaps Plan on a Jira DC instance with JVM locale de_DE causes Number Custom Field values to display with the decimal separator stripped | CLOSED
- Public Security Vulnerability | JRASERVER-79546 | Arbitrary File Access in Jira Data Center | PUBLISHED
- Bug | JRASERVER-79541 | Jira Logging and Profiling UI displays a "root" logger at DEBUG level starting in Jira 11.3.5 | CLOSED
- Bug | JRASERVER-79539 | G1 Old Gen not reclaiming, causing jobs stuck in Queued and rising JQL resilience blocks | CLOSED
- Bug | JRASERVER-79536 | OpenSearch index lags when migrating from Lucene in Jira DC | CLOSED
- Bug | JRASERVER-79534 | Performance degradation in Jira 11.3 due to serializing application property reads | CLOSED
- Bug | JRASERVER-79520 | Users Are Unable to Manage Sprints via REST API when they Do Not Have Admin Permissions | CLOSED
- Bug | JRASERVER-79517 | Remote issue link picker returns empty results when the current Cloud project key doesn't exist on the linked DC instance | CLOSED
- Bug | JRASERVER-79512 | Issue key in panel title shifts to panel body after editing in Visual Mode | CLOSED
- Bug | JRASERVER-79511 | Restarting nodes replciates JiraDelegatingDirectoryInstanceLoader cache causing HIGH IOPS and outage | CLOSED
- Bug | JRASERVER-79510 | Upgrading Jira Data Center to version 11.x on an existing index results in startup failure due to DocValues type mismatch | CLOSED
- Bug | JRASERVER-79509 | OpenSearch node skips Lucene updates during ZDU migration | CLOSED
- Bug | JRASERVER-79499 | Backlog requests can cause OOMEs on Lucene by retaining unbounded search results in memory | CLOSED
- Bug | JRASERVER-79489 | Component Lead cannot be saved in Microsoft Edge unless the user is selected twice | CLOSED
- Bug | JRASERVER-79486 | "No Filter/Project selected" error happens when editing Recently Created Chart gadget after upgrade | CLOSED
- Bug | JRASERVER-79484 | Watchers Dialog → UserPickerBrowser.jspa (Issue → More → Watchers) is extremely slow | CLOSED
- Suggestion | JRASERVER-79474 | MinAggregation missing from com.atlassian.jira.search.aggregation.metric in jira-api | CLOSED
- Bug | JRASERVER-79468 | Index failing with DocValuesField too large | CLOSED
Showing 20 out of 26 issues
Original source - Oct 5, 2026
- Date parsed from source:Oct 5, 2026
- First seen by Releasebot:Oct 24, 2026
Issues resolved in 10.2.19
Confluence releases version 10.2.19, a bug-fix update addressing security vulnerabilities across dependencies and a responsiveness issue in Confluence Data Center.
The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.19, which is a bug-fix release.
Don't have Confluence 10.2 yet?
Check out the new features and other highlights in the Confluence 10.2 release notes.
Get the latest version
We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.
- CONFSERVER-104520 — BASM (Broken Authentication & Session Management) io.netty:netty-handler Dependency in Confluence Data Center
- CONFSERVER-104516 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104510 — BASM (Broken Authentication & Session Management) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104509 — MITM (Man-in-the-Middle) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
- CONFSERVER-104507 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104488 — Arbitrary File Access in Confluence Data Center
- CONFSERVER-104459 — Confluence 10.2 can become unresponsive when requests wait on a stalled cache load
- CONFSERVER-104519 — Path Traversal (Arbitrary Read/Write) postcss Dependency in Confluence Data Center
- CONFSERVER-104518 — DoS (Denial of Service) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
- CONFSERVER-104517 — BASM (Broken Authentication & Session Management) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104515 — DoS (Denial of Service) com.fasterxml.jackson.dataformat:jackson-dataformat-cbor, tools.jackson.dataformat:jackson-dataformat-cbor Dependency in Confluence Data Center
- CONFSERVER-104512 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104511 — DoS (Denial of Service) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
- CONFSERVER-104508 — PrivEsc (Priviledge Escalation) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
- CONFSERVER-104506 — MITM (Man-in-the-Middle) io.netty:netty-handler Dependency in Confluence Data Center
- CONFSERVER-104504 — DoS (Denial of Service) org.springframework:spring-expression Dependency in Confluence Data Center
- CONFSERVER-104503 — XSS (Cross Site Scripting) org.springframework:spring-web Dependency in Confluence Data Center
- CONFSERVER-104502 — DoS (Denial of Service) org.springframework:spring-webmvc Dependency in Confluence Data Center
- CONFSERVER-104501 — SSRF (Server-Side Request Forgery) fast-uri Dependency in Confluence Data Center
- CONFSERVER-104514 — DoS (Denial of Service) nanoid Dependency in Confluence Data Center
Showing 20 out of 27 issues
Original source - Sep 16, 2026
- Date parsed from source:Sep 16, 2026
- First seen by Releasebot:Sep 18, 2026
Autonomous testing with Jira and BearQ
Jira adds BearQ, an assignable AI testing agent that brings end-to-end quality checks into the delivery workflow. It uses Jira context to explore user journeys, generate adaptive tests, catch defects early, and create actionable issues with reproduction steps and evidence.
Close the loop between the code your team builds and the quality you ship by bringing an intelligent, assignable agent directly into your Jira workflow.
Today, teams are caught between high-maintenance test suites that break easily and generic AI tools that lack delivery context. When testing is disconnected from where work is planned, teams lose sight of user journeys, acceptance criteria, and release scope. The result is blind spots, late-stage defects, noisy test suites, and costly handoffs across product, engineering, and QA.
Getting quality right in an AI-native delivery cycle requires grounding testing in the requirements and decisions your team collaborates on every day.
That’s where BearQ for Jira comes in.
BearQ is an assignable agent that brings intelligent, end-to-end testing directly into the delivery workflow. Acting as an AI teammate assigned to Jira work items, BearQ explores user journeys, generates adaptive test coverage, catches defects early, and closes the loop between the code agents write and the quality your team delivers.
How it works
Ground testing in real delivery context
Traditional testing often starts with disconnected tickets, stale specs, or clunky handoffs. BearQ flips this model by turning Jira work items into living test context.
Once code is generated and a PR or preview environment is ready, assign the work item directly to BearQ or @mention BearQ in Rovo Chat to start testing. BearQ instantly parses acceptance criteria, technical requirements, and comment threads to author test cases, document reproduction steps, and actively explore browser behavior. Whether Rovo leads initial triage or BearQ jumps straight into validation, quality assurance stays embedded directly in your flow of work – eliminating manual context gathering and costly handoffs.
Adapt tests as your application evolves
Fast-moving product teams shouldn’t be held back by static scripts. As features iterate and workflows shift, maintaining brittle test scripts becomes a full-time job.
Powered by real-time Jira context, BearQ autonomously explores and maps your application, discovering untested user paths and edge cases that scripted tests miss. Because it generates tests that dynamically adapt as application behavior changes, delivery teams can catch regressions before staging and move from planned changes to validated results in minutes rather than days.
Scale QA capacity without losing control
Expand your testing footprint without sacrificing trust or governance. BearQ acts as an autonomous teammate, exploring and validating across your application, while your team sets the guardrails, directs focus, and retains oversight where it matters most.
When BearQ finds regressions, UX issues, or data inconsistencies, it creates actionable Jira issues with reproduction steps and evidence. Less time spent triaging means faster feedback, quicker resolution, and more time for QA to focus on high-impact risk.
Availability
BearQ for Jira is available on the Atlassian Marketplace. Connect BearQ to your Jira workspace today to bring testing and delivery together into a unified, agent-orchestrated workflow.
Original source - Sep 15, 2026
- Date parsed from source:Sep 15, 2026
- First seen by Releasebot:Oct 13, 2026
[Added] Access token, Forge app and Rovo Dev support for branch restrictions
Bitbucket expands branch restrictions to support repository, project, and workspace access tokens, Forge apps, and Rovo Dev in write and merge access rules at both repository and project levels.
What's changing
Branch restrictions now support adding the following to Write Access and Merge Access branch permissions in your branch restriction rules:
- Repository access tokens (RAT)
- Project access tokens (PAT)
- Workspace access tokens (WAT)
- Forge apps
- Rovo Dev
This applies to both repository and project-level branch restrictions.
What you need to do
No action is required. To use this feature, navigate to Repository settings → Branch restrictions or Project settings → Branch restrictions and add your access tokens, Forge apps or Rovo Dev to the desired permission rules.
For more information see our community post.
Original source - Sep 15, 2026
- Date parsed from source:Sep 15, 2026
- First seen by Releasebot:Sep 15, 2026
[Announcement] OAuth 2.0 3LO is now available for Trello
Trello now supports OAuth 2.0 authorization code grants with granular scopes, short-lived tokens and a new consent screen.
Trello now supports OAuth 2.0 authorization code grants for apps, featuring granular scopes, short-lived tokens, resource restrictions, and a redesigned consent screen consistent with other Atlassian products. New apps can opt in right away, and existing apps can transition when ready.
Read more on our developer community page - OAuth 2.0 is now available for Trello!
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.