User display names not resolved in Pie Chart when mixed user identifier types are present

XMLWordPrintable

    • 2
    • Severity 2 - Major
    • 1

      Issue Summary

      In Jira Cloud, when viewing the issue navigator pie chart for the Assignee field, some users are shown as internal IDs/UUIDs instead of their display names. This occurs when the chart data includes a mix of users whose user_name and external_id match and users whose user_name and external_id differ. The affected users’ names are visible elsewhere in Jira (e.g. on the issue view), so this appears to be a chart‑specific resolution bug rather than a privacy/permissions issue.

      Steps to Reproduce

      Precondition (data setup)

      • Have at least two users in the same instance:
        • User A where user_name = external_id
        • User B where user_name ≠ external_id
      • Assign some issues to User A and some issues to User B.

      Example (internal) SQL used by developers to identify such users:

      • Users with mismatched identifiers (external_id <> user_name):
        SELECT *    FROM cwd_user u    LEFT JOIN cwd_directory d ON u.directory_id = d.id    WHERE external_id <> user_name;
      • Users with matching identifiers (external_id = user_name):
        SELECT *    FROM cwd_user u    LEFT JOIN cwd_directory d ON u.directory_id = d.id    WHERE external_id = user_name;

      Repro steps (UI)

      1. In Jira Cloud, go to Issues → Search for issues (issue navigator).
      2. Build a filter that returns issues assigned to both User A (matching IDs) and User B (mismatched IDs).
        • For example, assignee IN (userA, userB) with at least one issue for each.
      3. From the issue navigator, click View as → Pie chart.
      4. Set Statistic type = Assignee.
      5. Observe the pie chart legend.

      Optional control case

      1. Build a second filter that returns issues assigned only to users with mismatched IDs (e.g. only User B and similar).
      2. Repeat steps 3–4 and compare the legend behavior.

      Expected Results

      • The Assignee pie chart should display the user’s display name for all users included in the chart, as long as the viewer has permission to see that name.
      • Users like User B (with user_name ≠ external_id) should show their normal display name in the chart legend, just as they do in the issue view and assignee field.

      Actual Results

      • When the chart includes a mix of users:
        • Users where user_name = external_id (e.g. User A) show correctly with their display names.
        • Users where user_name ≠ external_id (e.g. User B) show as raw internal IDs/UUIDs (their user_name value) in the chart legend instead of their display names.
      • When the chart includes only users with mismatched IDs (no “matching ID” users):
        • All users display correctly with their names in the legend.

      This indicates the resolution logic is incorrectly inferring the identifier type for the entire dataset and failing to resolve display names for users whose user_name and external_id differ, but only when mixed with users whose identifiers match.

      Workaround

      There is a partial, impractical workaround:

      • If the filter and chart are adjusted so that the result set only contains users from the same identifier group (for example, only users where external_id <> user_name, and no users where external_id = user_name), then all affected users’ names display correctly in the pie chart legend.
      • However, this requires administrators to manually curate filters to avoid mixing user identifier types, which is not a realistic long‑term solution for customers using charts across their real‑world data.

      If such filter adjustments are not feasible, users will continue to see internal IDs/UUIDs instead of display names for some assignees in the pie chart.

              Assignee:
              Unassigned
              Reporter:
              Illia B
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: