Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4120

When updating a custom field via API, only 250 characters are accepted.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.118.0
    • 10.106.4
    • REST API
    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      The PUT API for align Epic is failing if the custom field value is greater than 250 characters. Epic's "Justification" custom field by API is limited to only 250 characters. This is however not seen for any other field for example, description. There is also no character limit if we update the Justification (customfield_70001) field from the UI, with the same value as the API example

      Steps to Reproduce

      1. Run the following API call with the value for customfield_70001 which is more than 250 characters.
        curl -X PUT "https://<JA URL>/rest/align/api/2/Epics/<epic id>" -H "accept: */*" -H "Authorization: Bearer <token>" -H "Content-Type: application/json;odata.metadata=minimal;odata.streaming=true" -d "{ \"id\": 2463, \"title\": \"<title>\", \"themeId\": <theme id>, \"description\": \"<description>\", \"primaryProgramId\": <program id>, \"state\": 1, \"type\": 1, \"additionalProgramIds\": [<program ids>], \"customFields\": [ { \"customfield_70001\": [ { \"value\": \"<value more than 250 characters>"} ] }, { \"customfield_70002\": null }, { \"customfield_70003\": null }, { \"customfield_70004\": null }, { \"customfield_70005\": null } ],}"
        
      1. Check the output for the call

      Expected Results

      The API should be consistent with the UI.

      Actual Results

      We get a 400 error

      [
        "value must be between 1 and 250 characters."
      ]
      

      Workaround

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

            kforeman@atlassian.com Kyle Foreman
            sraj3@atlassian.com Sujay
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: