Fixed: Assets health check endpoints are timing out on Jira 10.3.10 LTS

Issues resolved in 11.3.2

• Bug JSDSERVER-16489 Misleading message showing due to user permission after first login-free created ticket.
• Bug JSDSERVER-16402 Approvers from Assets customfield can't be updated for issues created before the upgrade
• Bug JSDSERVER-16401 Assets health check endpoints are timing out on Jira 10.3.10 LTS
• Bug JSDSERVER-16218 Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value.
• Bug JSDSERVER-15740 Issues moved between projects retains original organization
• Bug JSDSERVER-14090 JSM Email Channels configured to use the Microsoft Graph API don't support GCC High customers
• Bug JSDSERVER-11467 Asset View : Button in the comment section does not have a label and has missing keyboard support.
• Bug JSDSERVER-11115 Insight Read-only Custom Field adds an entry in the Issue History even if there are no changes to that field
• Suggestion JRASERVER-79044 Jira Mail Handlers configured to use the Microsoft Graph API don't support GCC High customers
• Bug JRASERVER-79038 Plugin upgrade can take several hours due to lack of caching in permission checker
• Bug JRASERVER-78112 During an index snapshot restore Jira holds an exclusive write lock on the index but allows traffic unexpectedly when clustering is configured
• Bug JRASERVER-77507 Running a JQL search with many text clauses may cause an out of memory error
• Bug JRASERVER-76747 Editing the hostname for Custom Service Provider with MS_Graph protocol can only be done after switching between Service Providers
• Bug JRASERVER-74715 When searching by statusCategory QueryComponent!Jql.jspa
  returns 400 because of 'jqlTooComplex'