CurrentUser() but for the user ID?

[Jason Moerbe]

I know how to use CurrentUser() in gadgets to get info specific to the currently logged in user. But is there a similar variable that is specific to the currently logged in users ID rather than just their screenname? I have not been able to find that. I ask because on the activity stream gadget, when setting it to a specific user, you get different information when entering the screen name vs. the ID.

If you enter the screenname or CurrentUser(), the activity stream populates, but does not include everything like when the person inters an issue.

if you use the user ID, you get the more comprehensive list of activity.

[EddieW · Accepted solution]

Are you using activity-streams acrosss different tools? This sounds like an issue in the Actitvity Stream plugin, unless the different tools have different backend users.

[Jason Moerbe]

We have JIRA Agile, Confluence, Bitbucket, and HipChat. But its the same user base acroos those tools.

[Jason Moerbe]

So what I understand from your answer is that using a person's user NAME in a gadget filter is expected to return the same information that person's user ID intead?

[EddieW]

@Jason- use the 'continue discussion' link to keep this convo in thread, and not as new answers :).

Yes, I would expect currentUser() (which is an object containing both username and id) to work across all tools if the user info was identical (i.e. using Crowd and all our apps streams are integrated), and your mention of BitBucket makes me think that users commiting to git are only tied to their user IDs, you may need to setup aliases, but I would think that the activity stream would only be missing, not JIRA tickets.

I am more suspecting this to be a bug/issue, potentially related to https://jira.atlassian.com/browse/JRA-35013- I would check for related knowledge articles, and if nothing lines up, submit a support ticket.

[Jason Moerbe]

Thanks for the advice!

[EddieW]

Sure thing @Jason!

If you do find a resolution (yourself or through support) please come back and let us know!