Bitbucket UI displays an internal UUID instead of the corresponding human-readable name

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: None
    • Component/s: Bitbucket Cloud
    • None
    • ALL Languages

      The Bitbucket UI displays an internal UUID in the footer under the "Generated by" section instead of resolving the UUID to a human-readable name.

      Current display:

      Generated by 4f339e6a-f4b0-48e4-ad5c-845020f7f6f5. Cluster contains one node.

      The UUID appears to be an internal identifier that should be mapped/resolved to the appropriate display name where applicable.

      Steps to Reproduce

      1. Log in to Bitbucket Data Center.
      2. Navigate to a repository.
      3. Open the Pull requests page.
      4. Scroll to the bottom of the page.
      5. Observe the "Generated by" information in the footer.

      Actual Result

      The UI displays the internal UUID:

      4f339e6a-f4b0-48e4-ad5c-845020f7f6f5

      instead of a human-readable name.

      Expected Result

      The UUID should be correctly resolved/mapped to the corresponding human-readable name, or the internal UUID should not be exposed in the user-facing UI if no name mapping is applicable.

      Environment

      • Product: Bitbucket Data Center
      • Version: 9.6.5
      • Deployment: Data Center / single-node cluster
      • Page: Repository → Pull requests
      • Browser: Chrome Version 151.0.7922.138 
      • OS: Mac

      Frequency

      Always / consistently reproducible

      Impact

      The UI exposes an internal identifier instead of a meaningful human-readable value. This makes the information difficult for users to interpret and suggests that the UID-to-name mapping/resolution is not being performed correctly.

              Assignee:
              Unassigned
              Reporter:
              Samidha Halve
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: