Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25351

Rest API output from Jira server returning ID instead of name for 'Team' field

XMLWordPrintable

      Issue Summary

      Rest API output from Jira server returns unexpected value of team field to Confluence Cloud, ie, it is returning an ID instead of the team name. "Team" field is a custom field which is a part of Jira Advanced Road Maps.

      Steps to Reproduce

      1. On server use https://BASEURL/rest/api/latest/field to find the 'Team' field
      2. Use https://BASEURL/rest/api/latest/issue/ISSUEKEY find the field output

      Expected Results

      Jira should return name of the team field to Confluence Cloud, the same way it shows in DC Confluence.

      Actual Results

      However, the ID of the team field is returned from the Jira Server to Confluence Cloud, which is of no relevance to the end user.

      Workaround

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

        1. Actual.png
          Actual.png
          13 kB
        2. Expected.png
          Expected.png
          13 kB
        3. Screenshot 2023-10-20 at 4.02.05 PM.png
          Screenshot 2023-10-20 at 4.02.05 PM.png
          11 kB
        4. Screenshot 2023-10-20 at 4.03.12 PM.png
          Screenshot 2023-10-20 at 4.03.12 PM.png
          10 kB

            [JSWSERVER-25351] Rest API output from Jira server returning ID instead of name for 'Team' field

            Daniel Rauf made changes -
            Fix Version/s New: 8.22.0 [ 98792 ]
            Daniel Rauf made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Daniel Rauf added a comment -
            Atlassian Update – 7th November 2023

            Dear Customers,

            I've identified this issue as a duplicate of JPOSERVER-2911, which has been addressed in Jira version 8.22.0.

            I will proceed to close this issue due to the duplication. For more details, please refer to JPOSERVER-2911.

            Daniel Rauf
            Software Engineer

            Daniel Rauf added a comment - Atlassian Update – 7th November 2023 Dear Customers, I've identified this issue as a duplicate of JPOSERVER-2911 , which has been addressed in Jira version 8.22.0. I will proceed to close this issue due to the duplication. For more details, please refer to JPOSERVER-2911 . Daniel Rauf Software Engineer
            Daniel Rauf made changes -
            Link New: This issue duplicates JPOSERVER-2911 [ JPOSERVER-2911 ]
            Daniel Rauf made changes -
            Status Original: Gathering Impact [ 12072 ] New: In Progress [ 3 ]
            Daniel Rauf made changes -
            Assignee New: Daniel Rauf [ drauf ]
            Chandra Shekhar Pandey made changes -
            Remote Link Original: This issue links to "PSR-884 (Bulldog)" [ 833479 ] New: This issue links to "PSR-884 (JIRA Server (Bulldog))" [ 833479 ]
            Chandra Shekhar Pandey made changes -
            Remote Link New: This issue links to "PSR-884 (Bulldog)" [ 833479 ]
            Fernanda Reple made changes -
            Comment [ [https://getsupport.atlassian.com/projects/ACE/queues/custom/1110/ACE-4124] - Mega Migrator Amadeus is currently affected by this bug. This is causing delays in the migration timeline. This customer is under executive escalation. ]
            CST JAC Workato Bot made changes -
            Labels New: ACE-4158

              drauf Daniel Rauf
              13f27f9b2775 Jagriti
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: