Webhook events for issue changes use different url for user avatars

For the REST api v2, when I search for issues using the JQL search endpoint POST /rest/api/2/search, the user fields that come back (such as assignee) have avatarUrls. These urls load the users’ images properly when I navigate to them. I also have a webhook set up to track the same issues. When that webhook is triggered, the user fields it sends in the issue data have slightly different avatarUrls. These urls load generic initials-only images, not the users’ chosen profile images.

Why is this? Can I get the webhook to send the correct avatarUrls, not the placeholders?

The urls from the JQL query endpoint look like this (ids have been changed): https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/67103:8250b658-b5d4-11ec-bb93-1950bad24051/93e29fa5-b5d4-11ec-8198-03da6485edcf/48
The urls from the webhook payload look like this: https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/initials/JS-4.png

Hello @MatthewCheney ,

I believe this behavior is related to the profile visibility settings. However, in order to whether confirm or deny, can you check if you also get the placeholder in case the avatar visibility is set to “anyone”?

For further details on this please see:

I do get the correct url if the visibility is set to anyone.

I thought that creating the webhook with an authenticated user might be enough to satisfy the visibility settings. If the auth token used to create the webhook can also be used to read all user information, I would imagine the webhook could safely return all user information.

Not knowing much about the involved scenario, I can only say that this might be same/similar behavior to the one described in the already provided bug ticket and feature request: