-
Bug
-
Resolution: Fixed
-
Highest
-
5.12.20, 5.12.21
-
Severity 1 - Critical
-
93
-
-
Issue Summary
Assets custom fields are always populated with the same specific object.
This bug is a regression of JSDSERVER-15255 and it affects Jira Service Management (JSM) 5.12.20, 5.12.21.
This is reproducible on Data Center: yes
Steps to Reproduce
- Have more than 10000 Assets objects
- Setup an Assets custom field and add it to a project create screen.
- Create an Assets object that has the same id to the project; this Assets object need not match the custom field configuration or context. (You may have to create a number of objects, so that it reaches the count of project ID)
- Create a ticket or update the ticket without putting any values to the Assets custom field, or by changing the value / Assets object.
Expected Results
- After creating or updating the ticket with empty value for the Assets custom field, the field value remains empty.
- Changing the field value (setting a different object or clearing the value) works as it is supposed to.
Actual Results
- A specific Assets object has been populated in the custom field after creation or update, although the custom field value has not been set.
- When editing a ticket, changing or clearing the custom field value always sets the value back to the same, specific Assets object.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- relates to
-
-
- Closed
-
-
-
- Closed
-
- links to
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-16145] Assets custom fields can be populated with apparently "random" object(s) upon issue create/update action [Regression of JSDSERVER-15255]
| Remote Link | New: This issue links to "Page (Confluence)" [ 1010879 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1010340 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1008070 ] |
| UIS | New: 93 |
| Current Status |
Original:
{panel:title=Atlassian Update – 9 April 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
We have become aware of an issue with the previously recommended releases (Jira Software Data Center v9.12.21 and Jira Service Management Data Center v5.12.21) and they are no longer available for download. We are currently working to provide fixed versions Jira Software Data Center v9.12.22 and Jira Service Management Data Center v5.12.22 which are targeted for release within the next 24 hours. Thank you, Mateusz Marzecki Senior Engineering Manager {panel} |
New:
{panel:title=Atlassian Update – 9 April 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
We are glad to announce that the fix has been released in Jira Software Data Center v9.12.22 and Jira Service Management Data Center v5.12.22 Thank you, Raphael Biland Senior Software Engineer {panel} |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1006894 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Fix Version/s | New: 5.12.22 [ 111192 ] |
| Current Status |
New:
{panel:title=Atlassian Update – 9 April 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
We have become aware of an issue with the previously recommended releases (Jira Software Data Center v9.12.21 and Jira Service Management Data Center v5.12.21) and they are no longer available for download. We are currently working to provide fixed versions Jira Software Data Center v9.12.22 and Jira Service Management Data Center v5.12.22 which are targeted for release within the next 24 hours. Thank you, Mateusz Marzecki Senior Engineering Manager {panel} |