Understanding Bitbucket Cloud Pipelines UI User Avatar Filters

Summary

This knowledge-based article aims to identify the reason why the user avatar filters on the Bitbucket Cloud Pipelines home page UI do not display all users who have historically triggered Pipelines builds.

Diagnosis

1. Three or more developers/users have initiated their Pipelines builds in a repository, yet only two user avatars are displayed on the Pipelines home page UI.

2. In a repository with three or more developers or users, only one user is triggering Pipeline builds. However, other users can see their own avatars as well as the avatar of the user who triggered the builds.

   1. User A: Can see 2 avatars (their own and User B's avatar who triggers Pipelines builds)

   2. User B: Can only see his own avatar

The reason why this is the expected result

The user filter on the Bitbucket Cloud Pipelines home page displays the currently logged-in user and all users who triggered Pipelines builds from the first page only. It's important to note that navigating to different pages will not alter the user filter.

Based on the diagnosis provided, the observed result aligns with expectations due to specific criteria governing the functionality of the Pipelines home page UI filter:

1. This occurs because the filter exhibits the presently logged-in user and the user who initiated Pipelines builds on the initial Pipelines home page.

2. User A can view two avatars because the page displays the individual who initiated Pipelines builds on the initial home page, as well as the user who is presently logged in. In contrast, User B is unable to see other users' avatars because User B is listed on the first page, while others are not.