Fixed: Assets Object History is not being saved when history IDs exceed 2 billion
Issues resolved in 11.0.0
- The Atlassian Jira team is pleased to announce the release of Jira Service Management 11.0.0
- JSDSERVER-16340: Assets Object History is not being saved when history IDs exceed 2 billion
- JSDSERVER-16325: Issue XML export is missing the value from Asset Custom field
- JSDSERVER-16312: The Assets code which is inserting the default values for Assets custom field for a request type in JSM project contains a constraint which limits the custom field ID length to a maximum of 5 digits
- JSDSERVER-16296: Large number of request type causes, SQL exception error parameter limit "The server supports a maximum of 2100 parameters"
- JSDSERVER-16295: Filtering assets by Object type does not work, you can not select the Object type, instead you see on the filter: "Object type: all"
- - JSDSERVER-16282: Editing an issue as an agent starts an SLA configured for Resolution: Cleared event
- - JSDSERVER-16272: The Mail Audit logs of the JSM Mail handler reports an incorrect error when trying convert an empty email into a comment
- JSDSERVER-16266: Upgrade task 'AUT_0025_DeleteLeftOverCustomFields' failed with foreign key constraint violation
- JSDSERVER-16265: Increase varchar for TYPE_VALUE column on AO_8542F1_IFJ_OBJ_TYPE_ATTR table
- JSDSERVER-16256: Queue Count is hidden when selecting a Project Queue
- JSDSERVER-16252: Assets: Unable to move objects between different object types from UI when number of object-types in an object schema exceeds 1000
- JSDSERVER-16250: The Assignee column is not resized for large values in the Project Queue
- JSDSERVER-16249: Assets custom field values are not showing up via Jira Issues Macro on a Confluence page
- JSDSERVER-16246: Moving objects on the schema search and object view failed with error "The object type that you wish to move objects from, has inbound references from other Object type(s) that can't be kept due to configuration."
- JSDSERVER-16245: Accessing a saved filter that contains Assets object value with both its label and object key could result in an error page with NullPointerException
- JSDSERVER-16244: Agents are automatically redirected from a JSM issue to the JSM queue it used to belong to
- JSDSERVER-16234: Unreadable white text when performing bulk object edits in Assets.
- JSDSERVER-16220: Add new feature to configure max count for each view in Change calendar and also support backend filtering
- JSDSERVER-16219: The Jira change calendar view displays an error message stating "Too many events" instead of showing the scheduled changes for deployment in the Day, Week, Month, or List view or when trying to use the filter mentioned in the change calendar UI.
- JSDSERVER-16212: Without being in the Object Schema Managers role, the history of object attachment is not visible to users in the History tab