Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16145

Assets custom fields can be populated with apparently "random" object(s) upon issue create/update action [Regression of JSDSERVER-15255]

XMLWordPrintable

    • Severity 1 - Critical
    • 93
    • Hide
      Atlassian Update – 9 April 2025

      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

      Show
      Atlassian Update – 9 April 2025 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

      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

      1. Have more than 10000 Assets objects
      2. Setup an Assets custom field and add it to a project create screen.
      3. 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) 
      4. 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.

          Form Name

            [JSDSERVER-16145] Assets custom fields can be populated with apparently "random" object(s) upon issue create/update action [Regression of JSDSERVER-15255]

            Andrea Mura added a comment -

            Hi Team,

            we've completed the update (I had to manually download JSM version 5.12.21 and upload it), but unfortunately the issue still seems unresolved.

            For example, when I move an issue, the Assets fields are still being populated with random objects.

            Another symptom is that I’m unable to remove these random objects from the Assets fields once they’ve been inserted.

            We've also noticed that versions 5.12.20 and 5.12.21 seem to have been deprecated — they're no longer available in the download archive.
            Is a definitive fix expected to be released soon?

            Andrea Mura added a comment - Hi Team, we've completed the update (I had to manually download JSM version 5.12.21 and upload it), but unfortunately the issue still seems unresolved. For example, when I move an issue, the Assets fields are still being populated with random objects. Another symptom is that I’m unable to remove these random objects from the Assets fields once they’ve been inserted. We've also noticed that versions 5.12.20 and 5.12.21 seem to have been deprecated — they're no longer available in the download archive. Is a definitive fix expected to be released soon?

              bornatowski Bartosz Ornatowski
              bornatowski Bartosz Ornatowski
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: