Troubleshooting and Support for Jira

• Made "Secondary Storage - Index Snapshots" healthcheck run on Lucene only
• Added websudo enforcement in some endpoints
• Added app performance metrics collection that excludes custom apps
• Improvements on other metrics collection and processing

• Added websudo enforcement in some endpoints
• Added app performance metrics collection that excludes custom apps
• Improvements on other metrics collection and processing

• Added websudo enforcement in some endpoints
• Added app performance metrics collection that excludes custom apps
• Improvements on other metrics collection and processing

• Added performance metrics collection that captures response times for key user journeys including issue view, dashboard, boards, backlog, and search operations. The collected data supports Instance Optimization and additional Portfolio Insights features.
• Fixed to only return the numbers of Active projects to the Instance Optimization feature

• Added performance metrics collection that captures response times for key user journeys including issue view, dashboard, boards, backlog, and search operations. The collected data supports Instance Optimization and additional Portfolio Insights features.
• Fixed to only return the numbers of Active projects to the Instance Optimization feature

• Added performance metrics collection that captures response times for key user journeys including issue view, dashboard, boards, backlog, and search operations. The collected data supports Instance Optimization and additional Portfolio Insights features.
• Fixed to only return the numbers of Active projects to the Instance Optimization feature

• Fixed issue in Application links client credentials expiry health check which didn’t check external app links.
• Fixed issue in Instance Optimization feature which counted inactive Jira nodes in the number of nodes for the guardrails.

Added the `configContext` field to the payload sent to Atlassian Cloud as part of the Instance Optimization feature. Contains information to help determine the reason if some health indicators are missing from the payload.

Exclude System Applinks from Healthchecks

Added the `configContext` field to the payload sent to Atlassian Cloud as part of the Instance Optimization feature. Contains information to help determine the reason if some health indicators are missing from the payload.

• Mitigated possible false failures of the Applinks Health Check

• Fix issue with health check false results for unsupported collation
• Fix issue with possible false results of Applinks Health Check

• Added support for OpenSearch index replication consistency health check
  • Lucene snapshot and replication checks are disabled when running OpenSearch
• Small security fixes

Small security fixes

Small security fixes

• Minor update to text message displayed in the health check

• Supports new Platform version introduced in new Jira major version
• Introduces new health checks:
  • Basic Authentication Disabled Health Check, which makes sure that unsafe way of authenticating is disabled. More details on disabling basic authentication.
  • Applinks Credentials Expiration Health Check, which notifies about expired credentials for applinks. More details on application links.

Minor security bugfixes

• Minor security fixes

We made some changes for Optimization feature:

• Fixed a bug in which one of the guardrails was not fetched correctly under specific circumstances
• Updated behaviour of Get app on Marketplace button. Before, it opened entry for Cloud companion on https://marketplace.atlassian.com, now, it redirects to Cloud companion in Manage apps (Universal Plugin Manager).
• Sending data to cloud is enabled by default after creating connection to Cloud.

Bugfixes:

• Fixed minor security vulnerabilities

We made some changes for Optimization feature:

• Fixed a bug in which one of the guardrails was not fetched correctly under specific circumstances
• Updated behaviour of Get app on Marketplace button. Before, it opened entry for Cloud companion on https://marketplace.atlassian.com, now, it redirects to Cloud companion in Manage apps (Universal Plugin Manager).
• Sending data to cloud is enabled by default after creating connection to Cloud.

Bugfixes:

• Fixed minor security vulnerabilities

Monitor and optimize your instance performance

The new Optimization tab enables integration with Portfolio insights in Atlassian administration, providing actionable insights to optimize the health and performance of your Jira Data Center instance.To find the new Optimization tab, go to Settings > System > Troubleshooting and support tools. Learn more about optimization insights for Jira Data Center

Bug fixes:

• Fixed bug in Supported database Health check, which falsely informed that Azure SQL is not supported on Jira 10.x More details

The new Optimization tab enables integration with Portfolio insights in Atlassian administration, providing actionable insights to optimize the health and performance of your Jira Data Center instance.To find the new Optimization tab, go to Settings > System > Troubleshooting and support tools. Learn more about optimization insights for Jira Data Center

• Add supported databases check for Jira 10.3 and newer. Add new supported databases.
• JRASERVER-75949 Fix attaching support zip while creating support request in Get Help tab

JRASERVER-75949 Fix attaching support zip while creating support request in Get Help tab

Fixed https://jira.atlassian.com/browse/JRASERVER-78347

Fixed

• https://jira.atlassian.com/browse/JRASERVER-78347

For Jira 10.4 and above, Automation Queue health check has been added that would monitor:

• Automation Queue processing time. More details
• Automation Queue count. More details

Fixed issue with false-negative results of Security Vulnerabilities Health Check on products' version affected by High Severity CVEs

Fixed issue for End of Life Health Check in Jira 9.4 that incorrectly displays End of Life date. Related JAC ticket

Fixed false-negative results of Security Vulnerabilities Health Check on products' version affected by High Severity CVEs

- Fixed issue with Pre-upgrade planning tool not showing some of Jira 10 versions. More details

- Improved security by upgrading vulnerable dependency

- Fixed issue with Pre-upgrade planning tool not showing some of Jira 10 versions. More details

- Improved security by upgrading vulnerable dependency

• Improved security by removing local files created to be attached to the Support Zip after it is assembled.
• Support Zip now includes detailed information on the state and version of plugins and their modules.

• Improved security by removing local files created to be attached to the Support Zip after it is assembled.
• Support Zip now includes detailed information on the state and version of plugins and their modules.

• Adjusted the behavior of license user limit health checks to fail when the limit is reached
• Enhanced the audit log to track all configuration changes related to the license user limit healthcheck, not just the modifications.
• Implemented tracking for all license user limit configuration changes in the audit log
• Developed and integrated a user interface for configuring the license user limit healthcheck

• Updated license user limit health checks to fail when the limit is reached
• Enhanced audit logging to track all configuration changes related to the license user limit healthcheck.

• Included the seraph-config.xml file in the Jira Support Zip,

- Health check resource endpoints now have stricter access (from admin to sysadmin)

- Changes in configuration for the license user limit is now audited

• Improved security of the app

• Added compatibility with Platform 7. More details about Platform 7 changes

• Improved security of the app
• Extended analytic events sent from License Limit Health Check

• Fixed license limit warning false positive on unlimited user license instances. Bug ticket
• File application.xml within the generated support zip now has a consistent schema
• Expand gathered analytics related to cloud usage

• Improved format of health check results in support zip
• Bug with dismissing health check notifications was fixed. Bug ticket
• Added new license limit health check. More details

Local backups security health check has been added.

• Add Helm chart analytics of Openshift deployment
• JSDSERVER-15143 Allow Assets to create support zip
• Check for any XML backups in java.io.tmpdir directory

• CONFSERVER-92631 Log analyzer works with HTTPS proxy configured
• JRASERVER-76729 Users without admin access won't receive healthcheck email notifications
• ATST-1142 JRASERVER-76166 Fix failing healthcheck for MS SQL Server 2022

• Small fixes in UI translations

• Small fixes in UI translations

• Fix issue with creating unique file names while adding files to support zip

• Fix issue with creating unique file names while adding files to support zip

• New healthcheck to check the mail error queue is empty
• If the product is running in a Kubernetes cluster include the Helm file in the Support Zip

• New healthcheck to check the mail error queue is empty
• If the product is running in a Kubernetes cluster include the Helm file in the Support Zip

• Added info about license type to application.xml in support zip,
• Fixed End Of Life health check displaying incorrect End Of Life date. Related JAC ticket can be found here.

• Added info about license type to application.xml in support zip,
• Added Server End Of Life notification in Get help tab,
• Fixed End Of Life health check displaying incorrect End Of Life date. Related JAC ticket can be found here.

• Added index snapshot creation health check
• Added index snapshot existence health check
• Added SSO configuration to application.xml in support zip

• Added index snapshot creation health check
• Added SSO configuration to application.xml in support zip

• Small fixes in UI in "Create support zip" tab
• Added new information to support zip application.xml (list of enabled dark features, linux distribution details, indication of current node)
• Added new check to Plan your upgrade page
• Extended User Directories health check with names of failing user directories in error message
• Fixed JfrDumpingScheduler polluting log file

• Small fixes in UI in "Create support zip" tab
• Added new information to support zip application.xml (list of enabled dark features, linux distribution details)
• Added new check to Plan your upgrade page
• Extended User Directories health check with names of failing user directories in error message
• Fixed JfrDumpingScheduler polluting log file

• Reworked the UI for the Create support zip tab
• Users are now able to pick one of 4 file size limitation options (25/100/500 MB per file)
• Added an option to select logs based on the last file modification date: any time, today, or in the past 3/5/10 days
• The default maximum file size is now 100 MB per file
• Added new API parameters to support File modification date and Maximum file size options
• After creating a zip, the customization preferences are saved and shared across the instance
• Tomcat access logs are no longer limited to 5 most recent files
• Tomcat access logs aren't affected by file size limitation
• Added new health check for Crowd authentication

• Reworked the UI for the Create support zip tab
• Users are now able to pick one of 4 file size limitation options (25/100/500 MB per file)
• Added an option to select logs based on the last file modification date: any time, today, or in the past 3/5/10 days
• The default maximum file size is now 100 MB per file
• Added new API parameters to support File modification date and Maximum file size options
• After creating a zip, the customization preferences are saved and shared across the instance
• Tomcat access logs are no longer limited to 5 most recent files
• Tomcat access logs aren't affected by file size limitation
• Added new health check for Crowd authentication

• Stop logging inconsequential exceptions

• Stop logging inconsequential exceptions

• If JFR fails to start during server startup, ensure the server correctly reflects this by showing JFR as disabled.
• Capture the options selected for Support Zip creation into the application.xml file included in the Support Zip.
• Added PostgreSQL 15 support in Jira 9.10
• Added PostgreSQL 15 support in Jira 9.4
• Added Microsoft SQL Server support in Jira 9.10

• If JFR fails to start during server startup, ensure the server correctly reflects this by showing JFR as disabled.
• Capture the options selected for Support Zip creation into the application.xml file included in the Support Zip.
• Added PostgreSQL 15 support in Jira 9.10
• Added PostgreSQL 15 support in Jira 9.4
• Added Microsoft SQL Server support in Jira 9.10

JFR improvements

JFR improvements

Improve how JFR recordings work and improve healthcheck names and descriptions

Improve how JFR recordings work and improve healthcheck names and descriptions

• Fix bugs with JRF including problem parsing some Java versions. (ATST-1119)
• Security improvements
• Add mail server and mail batching notification configuration to application.xml in support zip

• Fix bugs with JRF including problem parsing some Java versions. (ATST-1119)
• Security improvements
• Add mail server and mail batching notification configuration to application.xml in support zip

• Security health check now checks for CVE-2022-26136, CVE-2022-26137, CVE-2022-26138
• Removed MSSQL 2016 as a supported database
• New mail queue health check
• Enabled thread diagnostics by default

• Security health check now checks for CVE-2022-26136, CVE-2022-26137, CVE-2022-26138
• Removed MSSQL 2016 as a supported database
• New mail queue health check
• Enabled thread diagnostics by default

Extend the JFR state analytic event

Extend the JFR state analytic event