Hey 0de38b1370d1 this ticket specifically asked for the "Ability to filter the API by account ID for instance". It sounds like your needs relate more to the gadget UI (not the REST API) which is a different request.

How do I identify the "account ID" for a team member? As per the ticket, this used to work by providing a username, which is readily accessible in the UI.

When viewing a user's page in your site's user management, the URL will contain the Atlassian account id. Depending on which user management setting is enabled for your org the URL will be structured as follows:
Original user management:
https://admin.atlassian.com/s/<site ID>/users/<Atlassian account ID>

Centralised user management:
https://admin.atlassian.com/o/<org ID>/members/<Atlassian account ID>

Here is a resource on determining which user management setting you have in your org source:

All that said, as my last comment shows you don't need the AAID to filter by user in the Activity Stream gadget. Have you tried using it? Typing in the username will return the user:

Above user's profile:

Hi Anusha,

How do I identify the "account ID" for a team member? As per the ticket, this used to work by providing a username, which is readily accessible in the UI.

Hey 0de38b1370d1 it's possible to filter by user within the Activity Stream gadget:

In fact, having tested it, the feature requested in this ticket appears to be working now:

Ability to filter the API by account ID for instance

https://<instance name>.atlassian.net/activity?streams=accountId=<Account ID>

Can you clarify what isn't working for you?

For me, I wanted to enable teams to use this to find the stream of activity by a given team member, not just for themselves, since many things like recently added comments, or reported time, or other activities related to an issue, cannot be found using standard issue search/filtering. I also wanted to be able to use it for my own activity in a separate dashboard.

Hi 0de38b1370d1 thanks for your feedback. Can you tell me more about how you currently use / would like to use the /activity?streams endpoint?

If there's demand for this feature that hasn't been reflected in the vote count here, I will either reopen this ticket or create a new one.

That said I think that this needs some more investigation on my end to determine how users are meant to be able to use the endpoint, as I haven't been able to find any recently updated documentation on the feature.

I will add comments here when I have an update. In the meantime, any context you can provide on your use case would be much appreciated. Thank you!

@Anusha Rutnam while I understand you have a process you are following, I believe relying on activity or upvotes is unrepresentative of need. I was not aware that this was required in order to keep an issue in consideration (perhaps because I didn't read some document Atlassian has tucked away somewhere - but I'd think I am fairly representative of many users of Atlassian products). Indeed, if the wider team I work in is representative, most people don't even bother to look for this issue tracking site, let alone ensure they are registered to post ideas and requests for features.

I am very disappointed in the approach taken.

PS: I spotted the "Feedback Policy" note now visible above, though have no recollection of previously seeing this...

It seems to me that the filter by username should remain supported by simply replacing the username with the new GUID for the user in the APIs. No need to change the API itself, just the data sent or returned.