Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-20760

REST API endpoint (Get user default columns) returns incorrect columns with duplicate custom fields

XMLWordPrintable

      Issue Summary

      REST API endpoint (Get user default columns) returns incorrect columns with duplicate custom fields

      Steps to Reproduce

      1. Create two Next-gen projects, each having a custom field of the same name, say Custom01. Alternatively, create one Next-gen project with its own custom field having the same name as one already existing.
      2. Run a JQL search (e.g. project = <Next-gen project 1>). Go to Columns->My Defaults and ensure the Custom01 column is checked. Export the output as XML or CSV (all fields).
      3. Execute the Jira REST API endpoint: Get user default columns

      Expected Results

      • The Custom01 column returned by the Jira REST API endpoint should match the one in the exported XML or CSV file.

      Actual Results

      • The Custom01 column returned by the Jira REST API endpoint may be one or the other duplicated field.

      Workaround

      Rename one (or more) of the duplicated custom fields so that their names are unique.

            [JSWCLOUD-20760] REST API endpoint (Get user default columns) returns incorrect columns with duplicate custom fields

            Dylan made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Short Term Backlog [ 12074 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels New: stale-bulk-close202109

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
            Kyle Painter made changes -
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            Kyle Painter made changes -
            Assignee Original: Kyle Painter [ kpainter@atlassian.com ]
            Kyle Painter made changes -
            Assignee New: Kyle Painter [ kpainter@atlassian.com ]
            Kyle Painter made changes -
            Component/s New: Next-gen - Configuration [ 60934 ]
            Component/s Original: REST API [ 46734 ]
            Alex Morgan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 506017 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            KP made changes -
            Description Original: h3. Issue Summary
            REST API endpoint ([Get user default columns|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-columns-get]) returns incorrect columns with duplicate custom fields

            h3. Steps to Reproduce
             # Create two Next-gen projects, each having a custom field of the same name, say _Custom01_. Alternatively, create one Next-gen project with it's own custom field having the same name as one already existing.
             # Run a JQL search (e.g. _project = <Next-gen project 1>_). Go to *Columns->My Defaults* and ensure the _Custom01_ column is checked. Export the output as XML or CSV (all fields).
             # Execute the Jira REST API endpoint: [Get user default columns|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-columns-get]

            h3. Expected Results
            * The _Custom01_ column returned by the Jira REST API endpoint should match the one in the exported XML or CSV file.

            h3. Actual Results
            * The _Custom01_ column returned by the Jira REST API endpoint may be one or the other duplicated field.

            h3. Workaround
            Rename one (or more) of the duplicated custom fields so that their names are unique.
            		New: h3. Issue Summary
            REST API endpoint ([Get user default columns|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-columns-get]) returns incorrect columns with duplicate custom fields

            h3. Steps to Reproduce
             # Create two Next-gen projects, each having a custom field of the same name, say _Custom01_. Alternatively, create one Next-gen project with its own custom field having the same name as one already existing.
             # Run a JQL search (e.g. _project = <Next-gen project 1>_). Go to *Columns->My Defaults* and ensure the _Custom01_ column is checked. Export the output as XML or CSV (all fields).
             # Execute the Jira REST API endpoint: [Get user default columns|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-columns-get]

            h3. Expected Results
            * The _Custom01_ column returned by the Jira REST API endpoint should match the one in the exported XML or CSV file.

            h3. Actual Results
            * The _Custom01_ column returned by the Jira REST API endpoint may be one or the other duplicated field.

            h3. Workaround
            Rename one (or more) of the duplicated custom fields so that their names are unique.

              Unassigned Unassigned
              kpillai KP
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: