Jira Core 9.6.x release notes
We're pleased to present Jira Core 9.6.
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
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.
Crowd membership changes batched during full and incremental directory syncs
Status: DONE
To improve the performance of Crowd membership changes, we’ve started batching them during full and incremental directory syncs. Besides, the requests for DirectoryManager lookups are now cached to boost the efficiency of the feature.
What’s supported?
During full and incremental directory sync, the following operations are supported:
- Bulk addition of nested group memberships to a group
- Bulk removal of nested group memberships from a group
- Bulk removal of user memberships from a group
Cache App API deprecated
Status: DONE
We’ve deprecated the Cache App API endpoint and hidden it behind the com.atlassian.jira.cacheResource dark feature flag. If needed, you can enable it. In future versions, the endpoint will be removed permanently.
Cache App API wasn’t intended to be used to flush all caches and is considered unsafe to be used in a production environment.
You might have used this API endpoint to avoid a full shutdown. But the implication that the endpoint has on Data Center may be equivalent to a full shutdown. Moreover, there’s no guarantee that an underlying issue will be fixed.
Now, for a cache flush event, we recommend performing a full restart. For Data Center, this means you should first shut down all nodes and then restart them.
jira.diagnostics.ipdlog.poll.seconds system property removed from In-product diagnostics
Status: DONE
In the In-product diagnostics tool (IPD), the system property jira.diagnostics.ipdlog.poll.seconds allowed you to change the interval at which the JMX values were polled and written to the log file atlassian-jira-ipd-monitoring.log. The default polling interval was and remains 60 seconds, while the property has been removed from IPD.
Known issues
The following table lists the issues that you might face in Jira Software 9.6. You’ll also find a workaround or temporary solution for each of them.
We are aware of these issues and have planned their resolution in future releases.
| Issue | Solution |
|---|---|
JIRA SOFTWAREClosed and completed sprints get automatically removed from the Sprint issue field when you’re moving issues to a new project. Since Jira 8.8, all sprints in the status “Closed“ have been automatically removed from the Sprint issue field when the user is moving issues to a different project. The goal of this behavior has been to remove irrelevant sprints from the velocity report. The user isn’t notified about the removal of closed or completed sprints, which results in data loss. Although now, the user can decide whether irrelevant sprints should display in the velocity report, the issues of data loss and insufficient transparency of the system behavior remain. | This is a known issue tracked in the ticket JSWSERVER-13333 - Getting issue details... STATUS We’ve come up with the following solutions for the issue and would like to know your opinion on them:
We’ll consider your feedback to develop and implement the optimal solution. |