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

Assets custom fields are always populated with the same specific object

XMLWordPrintable

      Issue Summary

      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.

      Expected Results

      This custom field has no values after creation or update. 

      Actual Results

      Assets object in different schema has been populated up in the custom field after creation or update. 

      Also occurs when editing a ticket.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

            [JSDSERVER-15255] Assets custom fields are always populated with the same specific object

            There are no comments yet on this issue.

              c8bcca445054 Benjamin Suess
              3d5a17e800ca Yufei Zuo
              Affected customers:
              1 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: