Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-76065

read_only fields longer the 255 characters accepted and render as null

XMLWordPrintable

      Issue Summary

      As reported in https://community.developer.atlassian.com/t/read-only-issue-field-returns-null-instead-of-contents-of-linked-json-property/45247, it appears that read only fields are limited to 256 characters in length. It should not be possible for Jira to accept longer field values such that it incorrectly rendered the field as null.

      Steps to Reproduce

      1. Create a read_only issue field.
      2. Set a value that is 256 characters or longer in length.
      3. Define a filter that includes the isue.
      4. View the filter in list mode with the field visible.

      Expected Results

      At step 4, the field renders as expected. Alternately, at step 2 the request to set the field is rejected.

      Actual Results

      At step 4, the field renders as "null". 

      Workaround

      None

        1. screenshot-1.png
          screenshot-1.png
          248 kB
        2. screenshot-2.png
          screenshot-2.png
          343 kB

            [JRACLOUD-76065] read_only fields longer the 255 characters accepted and render as null

            Matthew Hunter added a comment -
            Atlassian Update - November 20, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - November 20, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              dmorrow@atlassian.com Dugald Morrow
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: