Jira Core 9.3.x release notes

Jira Core release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Upgrading from 8.x to 9.x triggers full Jira reindex that causes some downtime during the process. If you’re on 8.x now, make sure you’ve estimated the downtime and set the best time for the upgrade.

Learn more about how to handle full reindex and estimate downtime

Jira Core 9.3 has a known issue that is causing the Atlassian Jira Diagnostics app to create excess threads, which leads to a degradation in performance. In situations of elevated database activity — for example, during a full reindex — this may lead to the entire instance crashing.

We’ve already delivered a fix for this problem in Jira Core 9.4.0, which is available for download. The same fix will be backported to Jira Core 9.3.2.

 More

Read the upgrade notes for important info about this release and see the full list of issues resolved.

 Compatible applications

If you're looking for compatible Jira applications, look no further:

 Good to know

If you're thinking to move to Data Center, check our recommendations first. See: Infrastructure recommendations for Jira.

Multi-threaded index catch-up (Data Center)

Index catch-up is now performed in multiple threads to increase scalability and speed up the node start-up on your Jira instance. Multi-threaded index catch-up prevents the hindrance caused by the synchronization between an obtained snapshot copy and the changes between the time of snapshot creation and the time of the node start-up.

As a result, you get the more effective use of computing resources and improved instance performance.

The feature goes out of the box. Multi-threaded index catch-up launches during start-up, when index snapshot is used, as well as during index recovery from a backup.

Learn more about Jira index

Learn more about Jira index snapshots

Improved accuracy of app attribution for database usage

We’ve added two new system properties into the Jira Diagnostics plugin to improve the db.core.executionTime metric and thus, to increase the accuracy of app attribution for database usage.

Enabling the properties allows attributing apps for database usage more accurately and reduces the impact of the operations on the instance performance.

  • com.atlassian.diagnostics.db.static.method.invoker.enable attributes an app for using the database by identifying a responsible plugin via the stack trace. The stack trace has the following properties:
    • atlassian.diagnostics.traversal.limit.stack.trace indicates how far into the stack trace to look.
    • atlassian.diagnostics.classname.pluginkey.map.disable set to false will disable the generation of a map of class names to plugin keys. This property helps decide which plugin is which in the stack trace.
  • atlassian.diagnostics.db.static.method.invoker.improved.accuracy.enable attributes an app for using the database by deciding which plugin is responsible via the class context.
    • The class context is similar to the stack trace but more accurate. The class context provides access to the loaded class and not just the class name. The class context has the following property: atlassian.diagnostics.traversal.limit.class.context that indicates how far into the class context to look.

Learn more about application metrics

Learn more about the Jira diagnostics plugin

New database connectivity metrics for in-product diagnostics

The new database connectivity metrics allow efficient instance diagnostics and timely resolution of performance issues. By using the metrics, you’ll identify what in your environment or infrastructure might impact the performance. Early discovery of a problem guarantees that it can be fixed before its consequences have a bigger impact on instance operation.

The metrics are available through JMX and a new log file atlassian-jira-ipd-monitoring.log.

The log file is available in the {jira_home}\log folder where you can find all the existing log files. The log file is also included in the Support Zip file. If needed, you can generate it in the Atlassian troubleshooting & support tools plugin and send the file to Atlassian Support.

The feature is enabled by default. 

Learn more about the new database connectivity metrics

Activity tabs failures fixed

We’ve investigated the issues that started occurring in the use of Activity tabs after the improvements released with Jira 9.0. The fix for the original Jira-related problem that we discovered has been released with Jira 9.1.1 and 9.2.0. But this primary solution didn’t fix the issue for all customers. We’re aiming to provide the final solution in Jira 9.4.0 LTS.

Through our investigation, we’ve also identified that there may be some issues that are caused by some third-party plugins, outside of Atlassian’s control. We're working with known partners regarding the issues and have set a path to find the proper root cause.

We’re also providing you with the list of things that you should report to Atlassian Support in case of failures in the Activity tabs.

  • Check the console for any suspicious errors or logs
  • Let us know on what page the issue occurs, along with the list of enabled plugins for the instance
  • Outline reproduction steps we should follow to replicate the issue

Resolved issues

Issues resolved in Jira 9.3.0

Released on  

T Key Summary Status
Loading...
Refresh

Issues resolved in Jira 9.3.1

Released on  

T Key Summary Status
Loading...
Refresh

Last modified on Nov 21, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.