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

Creating an Epic via API ignores multiple customfields

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 10.113.0
    • None
    • REST API
    • 1
    • Severity 3 - Minor
    • No

    Description

      Issue Summary

      I am able to reproduce this in alignsupport.  If you do a POST on the /align/api/2/Epics endpoint and pass it multiple values under customfield, it will ignore everything after the first customfield.  

      No errors returned

      Steps to Reproduce

      1. Do a POST on the /align/api/2/Epics endpoint to create an epic.  Example JSON I used below.  Adjust IDs to your environment needs:
      {
      		"title": "Lorem Ipsum Title 2",
      		"description": "Lorem Ipsum Description",
      		"primaryProgramId": "584",
      		"state": "1",
      		"type": "1",
      		"startInitiationDate": "7/1/2023",
      		"targetCompletionDate": "12/31/2024",
      		"customFields": [
      			{
      				"customfield_70001": [
      					{
      						"value": "ACC"
      					}
      				],
      				"customfield_70002": [
      					{
      						
                              "value": "klein - 100 - 1.000 AT (FB/IT)"
      					}
      				]
      			}
      		]
      	}
      

       

      Expected Results

      The epic will be created with data for both customfields that were indicated in the POST

      Actual Results

      If you do a GET for the epic that was created, you will see that only the first customfield was populated.  All subsequent data was ignored.  No errors were thrown during the running of the POST.

      Workaround

      No known workaround

      Attachments

        Issue Links

          Activity

            People

              csmith1@atlassian.com Cap Smith
              b9109d53fd18 Todd Hall
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync