Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. 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

XMLWordPrintable

      Issue Summary

      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.

      The code contains the following if as also confirmed by devs:

      if (customFieldId.length == "XXXXX".length) {
      

      Steps to Reproduce

      1. Have an Assets custom field with the length of ID longer than 5 (e.g. customFieldId_14441628).
      2. Set a default value for this custom field in a JSM project request type.

      Expected Results

      The default value is saved, other connected functionalities such as other Assets custom fields filtered based on this are working properly

      Actual Results

      The default value is not set, related functionalities are broken.

      Workaround

      Following our official guardrails, try to avoid creating more than 1200 custom fields over the Jira instance. However, as the custom field ID is incremented to the next 100 after every Jira restart for some historical reasons, deleting and recreating custom fields could theoretically lead to a situation with a custom field ID having a length more than 5 digits anyway.

      Versions Tested

      Testing Requirements Version Affected Version
      Customers Reported Version 5.12.16 Yes
      Other versions All versions Yes

              c8bcca445054 Benjamin Suess
              tmarchionni@atlassian.com Tiziana Marchionni (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: