issuekey in updatedBy(user) does not work as expected

[Derek Woods]

When my query looks like this:

issuekey in updatedBy(will)

I will get results that include users will, willy, william, etc.

If I try:

issuekey in updatedBy("will smith")

I will again get results that include users will, willy, william, etc.

If I try:

issuekey in updatedBy(547851:f5eec6f3-6b71-18d9-96bg-f1415b89d30)

which is will smith's identifier, I get a message "this user doesn't exist"

What do I need to do to get results only for "will smith"?

[Vsevolod Romanchenko]

You need to insert user's email

issuekey in updatedBy("email@gmail.com")

[Sten Kultakangas]

issue IN updatedBy(<email>) will obviously not work. The current implementation of the updatedBy function is usable only if you lookup the account ID by opening the user profile and copy the ID from the URL. In my opinion this is clearly a defect. Is Atlassian going to fix it ?

updatedBy must be able accept the value returned by the currentUser() function