Read-only issue field returns null instead of contents of linked json property

Hi, we have an a single customer with a single JIRA issue where one of the read-only custom jiraIssueFields (i.e. linked to JSON property) is not updating and is strangely reporting a value of ‘null’ within Jira

Any ideas as to what could cause this type of anomalous problem with a single issue. We have no reports of this occurring in any of several thousand other issues. But this issue is persistent, even after adding a 5th signature, one of the fields updates, but the other remains persistently “null”.

Custom Issue fields visible within Jira, the Signature Export field is “null”

excerpt from property: esign.digitalrose.dev

    "signeeList": "James XXXX, Narender XXXX, Jim XXXX, Rajesh XXXX, Farm XXXX",
    "export": "James XXXX, Distinguished Architect, Feb 6 2021 6:45 PM, Approval\nNarender XXXX, Sr Architect, Feb 6 2021 6:49 PM, Approval\nJim XXXX, Distinguished Architect, Feb 6 2021 7:22 PM, Approval\nRajesh XXXX, Sr Architect, Feb 8 2021 7:25 AM, Approval\nFarm XXXX, Dev Lead, Feb 15 2021 7:09 PM, Author",

excerpt from atlassian-connect.json

jiraIssueFields: [
 {
                "key": "signee-list-field",
                "name": { "value": "Signed By" },
                "description": { "value": "eSign: List of users who executed signatures" },
                "type": "read_only",
                "property": {
                    "path": "signeeList",
                    "key": "esign.digitalrose.dev",
                    "type": "string"
                }
            },
            {
                "key": "export-field",
                "name": { "value": "Signature Export" },
                "description": { "value": "eSign: Exportable list of Signatures (Name, Title, Date, Meaning)." },
                "type": "read_only",
                "property": {
                    "path": "export",
                    "key": "esign.digitalrose.dev",
                    "type": "string"
                }
            }
]

Thank you
Chris

1 Like

Update.

In case someone else hits this, through trial and error we determined that Jira has a 256 character limit on read-only string issue fields linked to JSON properties. If the JSON property is 256+ characters in length, the field in JIRA shows “null”.

If less than 256 characters the field shows the JSON property data accurately. This limit for read-only fields should probably be documented here: https://developer.atlassian.com/cloud/jira/platform/modules/issue-field/

3 Likes

Hi @Chris_at_DigitalRose,

It seems that Jira shouldn’t allow itself to get into a state where it can’t render the field. I’ve created JRACLOUD-76065 to get this fixed.

Regards,
Dugald