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

REST API 2.0: No custom field information returned when using Query Parameters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.121.0
    • 10.105.3, 10.107.4, 10.110.2
    • REST API

      Issue Summary

      Whenever you issue a REST API GET request to retrieve a single feature/epic (using the id path param), the custom fields information is returned according to the API 2.0 Custom Field Supportdocumentation
      However, if you are retrieving the features/epics using a query parameter (id or filter) you do not get the customFields information returned but get Null instead for the exact same feature.

      Steps to Reproduce

      When you get the feature/epic by id (path param) or no query param (to filter for example) you get the customFields information returned

      When using a query parameter (id or filter) you do not get the customFields information returned but get Null instead

      Expected Results

      Output for the customer fields is the same if you filter of not features/epics

      Actual Results

      Output for the customer field is different if you filter of not features/epics

      Workaround

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

        1. NoQueryParam.png
          NoQueryParam.png
          361 kB
        2. QueryParamUsed.png
          QueryParamUsed.png
          400 kB

              kforeman@atlassian.com Kyle Foreman
              646db21d89d1 Francois Panaget (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: