UpdatedBy() search filter is available for Jira Software, but still not for Jira Service Desk. Please also vote on: https://jira.atlassian.com/browse/JSDSERVER-7008 to add this functionality to ServiceDesk. Thanks!

It would be really a benefit for our company.

as mentioned by the previous comment, this function is bugged. It is not possible to call updatedBy(currentUser()) ... This must be clearly a bug. Hope it gets fixed in less than 10years fingerscrossed

EDIT: New feature request regarding this  issue: JRASERVER-70497 *https://jira.atlassian.com/browse/JRASERVER-70497*

Unfortunately, this new JQL function does not accept relative functions are arguments Usage of this function is then quite limited.
E.g. this won't work: issue in updatedBy(currentUser(), startOfWeek())

I also agree with @Isaac.nl that this functionality is helpful but that the UpdatedBy(membersOf("GroupName", "ProjectRole") added pivot would be hugely helpful.

Nice addition, although a bit limited. We use groups and project roles, so it would bring more benefit if we could search for "updatedby(project-role)" or "updatedby(group)". 

My apologies - I missed the extra bit of the syntax and was trying to use it by itself. Thanks for pointing me in the right direction. This will make things so much easier!

Hi mark.walker1, this feature is in the release. Could you share your syntax so I can have a look on your usage, please? Example syntax :

More about syntax:
https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-functions-reference-939938746.html#Advancedsearching-functionsreference-approverupdatedBy()

We have just updated to 8.0.1 server and trying the use the new updatedBy search filter but it doesn't validate? Did it actually make the final release?

Isaac, I haven't seen a response to your question from September 6th, so I took the liberty of asking the question on your linked ticket to see if we have any luck over on that side of the house. Here's hoping!

Fantastic, will it be available for Cloud as well? JRACLOUD-1973

Hi everyone,

We would like to inform you, that we have finished working on the ”Updated by" search filter in Jira Server.

It will be released in Jira Server 8.0 in the advanced search. We will share more details regarding this suggestion in the release notes of Jira 8.0.

Once Jira Server 8.0 is released we will inform you in this ticket. For now this feature is available through our Early Access Program (EAP) for Jira 8.0 - starting from EAP2: https://www.atlassian.com/software/jira/download-eap.

Kind regards,
Grażyna Kaszkur

Product Manager, Jira Server

@Nick the backstory is simple, Atlassian just had breed more programmers and train them for 15 years. Now that the breeding/training Jira ticket is complete, we can hope for some results!

@Jakub Reczycki Its all in your hands now.

@Greg - I had a similar thought. Also consider Atlassian's history of saying "we're going to work on this" and then nothing happens, such as: CLOUD-7184 which hasn't been updated in over a year since it was supposed to have been completed.

That said, Atlassian even acknowledging this is good news, and should be taken as such. Just, no one get your hopes up too high, and certainly don't plan anything based on this. I'll believe it when I see it.

Frankly I think expressing gratitude that a basic enhancement request that has been open for 15 years is being worked on is being far too kind to Atlassian.

Thanks, this filter would make things so much easier for me! I need a monthly report on users activities

Awesome

This is INCREDIBLY welcome news! I 100% needed this last night again and was frustrated. To get this email update has made my whole morning!!!

 THANK YOU!!!

+1  (we should open a ticket to have a (thumbsup) on comments!)

This is amazing news!

Hi everyone,

Thank you for your votes and comments.

The Jira Server team has reviewed the suggestion again based on your recent comments and votes.

We have added this suggestion to our roadmap and started working on it.

"Updated by" search filter in Jira Server will be included in one of the future Jira Server releases.

Kind regards,

Grażyna Kaszkur
Product manager, Jira Server

I also need this feature to keep track of when partners have responded to our tickets' questions or when they are languishing.

I was just looking for this today, as someone made a change to 500 tickets via a bulk change.  Scrolling thru the Activity Stream via the System Dashboard is less than ideal.  Luckily had the timeframe for the tickets down to about 5 days so I could find with a created query.   It would have been easier with an Updatedby type of query that I wouldn't have to purchase an addon!!

This JQL would need to have a history to it, so you could say "updated by X between Y and Z", so it's a little more complicated than just adding a field. But Jira already supports history for a few fields so this isn't a brand new concept they'd have to implement from scratch.

Added my vote #659

I am trying to understand why Atlassian is holding this back. Interestingly I can't think of a sound reason or technical impediment for this feature not to be implemented easily. 

Each issue is already re-indexed after each update. It does not matter whether you update the issue from the UI, REST API or Java API; if you are doing something that will appear in the issue history, you are always acting in the context of a user. 

UpdatedBy field should only act as a new system field that is indexed. Each issue already has tons of text that is indexed. This is only one user field, not a multiline text field, so shouldn't cause the issue's index data to get crazy large. It is pretty much the same as reporter or assignee fields.

So what could be causing this much trouble?

" This issue has 637 votes as of now with 300 watchers"

yes only in this thread, and there are at least 3 almost identical so it looks like Atlasian have his customers in place where the sun does not reach

I've just change my employer and previous one have a different product... there was no problems withthings simple as that:/

This issue was created for Jira version 2.3 (in 2003) and now we are in 2018 with at least Jira version 6.4 and still this is not possible! - This issue has 637 votes as of now with 300 watchers! - This should be a clear indication that this is an important and awaited feature (also for us). So please listen to your customers!

I also highly agree with the above comments that e.g. the "rich text editor" is not something highly important! There are more important things like this issue and others!

As per @MollyJo's comment, as a company we can already workaround (and are) all the other Jira issues stated by @Katarzyna in the description.  This however cannot be worked around.  And in fact implementing this issue would assist further with workarounds for the verbose email notifications as I can specifically ignore commentary/updates from automated integrations by a specific user more readily.

@MollyJo I assure you that you are not the only one. My organization would take zero benefit from these "priorities".

I agree with MollyJo. It's very easy to adjust email notification settings or set up a filter in my inbox to get more or fewer emails from JIRA. But to have to pay more money to yet another company to do a simple task? That is a rather odd solution.

Maybe I'm the only one, but I believe that this feature would be much more impactful then the "Improved Rich Text Editor", "Handling Jira email chattiness", or "Allowing users to edit shared filters and dashboards."

I mean, JIRA sends a ton of emails but that's something I can work around by just deleting them. Without paying money to an additional company, I cannot work around not having this feature.

While I appreciate the latest update by Atlassian, I'm just not convinced that this is something that'll take a tremendous amount of effort to implement. 

Hopefully you'll re-evaluate the request to be fundamentally important when this vote hits its 15 year mark.

Typical Atlassian response: "We won't include basic functionality that makes user experience sense, but you can buy it from someone else on our marketplace"... Jira has turned into an expensive solution with far too many additional micro-transactions. The data is all there, give a native ability for users to use JQL to parse some of the data PLEASE.

What it is, is ridiculous.

It is just so beyond unfortunate that this hasn't been added yet. It would make JIRA's native reporting so much more powerful.

Whilst I might be able to use a paid plugin to filter on last updated by, I still cannot add a simple column that shows the last modifer/updater of an issue, which I sort upon and export to csv.  This is a pretty basic request.

The idea of installing more add-ons into each of the applications increases the risk of it breaking, duplication of functionality, possibly unfeasible to upgrade as "that" add-on may no longer be supported. It is never a good idea especially for an Enterprise level installation to continuously install more applications. This would be akin to installing more and more software onto your computer because one small thing that you need is available in an add-on that has other functionalities you don't need.

@Daniel This is something that is so basic that Jira should incorporate into it's main JQL functionality... We should't have to pay for an add-on for basic functionality that should have, and can be, included in the first place. 

yep, ticket should just be closed, not sure why it is left open

Hey guys, this feature is implemented in JQL Search Extensions for JIRA (both server and cloud). It's very easy to use and your JQL looks like updatedBy="John Smith". It also comes with many more custom JQL keywords that are required by some users.

It's unlikely Atlassian will implement a feature that is only required by a handful of users. Especially that there are plugins available to address the need.

Here's a crazy idea... since Atlassian seems to think that this issue is closed, we could all open new issues around this topic to let them know how much of a demand this feature is (by so many users).... 

This is now becoming a requirement for my reporting at my agency since we have a team of people.  We use JIRA for for all our work tracking, but we change the Assignee frequently.  There is no way to report based on an individual's work using this system without it.  If this is not something that is going to be implemented soon, we may have to consider replacing with a different product.

Yet ANOTHER very basic need that is not supported in JIRA?

Seems like every time I search for some functionality there is an item like this, it is years old and JIRA is not doing squat about it.  

Yes I am sure they are (laying on sarcism pretty thick here)  - this ticket is older than the hills

 any update on this issue?

JIRA planed it on any sprint this year?

I request a related to this request is to be able to report with the field: "Last Modified by"  or "Last Updated by" matching the "Updated" date.  thnx.

It is shocking that this is not a built in feature - and even more shocking that JIRA is not even considering implementing this basic reporting filter. If JIRA is relying on add-ons to provide basic functionality, why would I as a client use the system when I could have something that encompasses everything I need?

@Dave Meyer For as many people that are still requesting this... and because this seems like it should be core functionality (not something that should require a third party plugin) I'd request that you re-evaluate your decision. Or at the very least close this ticket vs. leaving it in an open - unresolved status.  

I also vote for this feature...