@Atlassian Another spam comment from Himanshu Chowdhury.

This is one of the best technical sites that I was seen. I will buy web hosting by doing OVHCloud login and will take a website like yours.

updatedBy() JQL syntax exists and is documented here.

With this in mind, I would like to suggest this issue can be closed. 

p.s. Please note there is currently a bug affecting searches where the results contain more than 32,000 updates: JRACLOUD-79113 – JQL function UpdatedBy() not returning valid results

df0a2811afa5 Unfortunately the syntax you've described is not supported, but we have a feature request here: JSWCLOUD-23551 – Allow functions to be inserted into Updatedby()

I'd like to use currentUser() as an argument to updatedBy() which currently results in a syntax error (issuekey in updatedBy(currentUser()) results in Error in the JQL Query: Expecting ')' or ',' but got '('. (line 1, character 34)). Would it be a new feature request to be able to nest search filter functions inside of each other?

Shamelessly dropping an addon suggestion in here, might be helpful 

We just launched our new Activity and Reports webapp for Jira Cloud currently in beta and would love to hear your feedback on this.

Among other features it can provide a filtered activity feed for one specific or multiple users.
Also you can visualize your filtered activity in interactive charts and reports.

Oh and it can merge activity from multiple Jira Cloud sites.

If you are keen to try out a modern activity feed and report webapp for Jira Cloud then head over to deffo.io and sign up for the Beta, it's free and no installation is required 

Hi any idea when or how we can get this feature, our Cloud instance currently does not have the UpdatedBy filtering functionality as per:

According to both release notes for cloud and the cloud documentation this is implemented. However, it is not working and Atlassian Support suggested I vote for this feature.

Release notes: https://confluence.atlassian.com/cloud/blog/2019/12/atlassian-cloud-changes-dec-23-to-dec-30-2019

Documentation: https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-functions-reference-764478342.html#Advancedsearching-functionsreference-updatedByupdatedBy()

The bug is tracked in https://jira.atlassian.com/browse/JRACLOUD-73671

Facing the same issue as Jens mentioned above. Any ETA on the fix here, or any workaround?

Hi Ben. The part that is not working is the date filtering part. When I search for issues I updated in the past XX days, the results include issues that I updated more than XX days ago (but were updated by someone else in the specified time period).

Support has confirmed that this is not working correctly.

Actually, Jens, it's looking like it does work. I have Jira Cloud as well, and it worked just fine for me! Would you mind checking your syntax? I found that it returns a list of keys, so you'd have to say something like

issuekey in updatedby(user.name)

or

issuekey in updatedby("First Last")

where user.name is the user's username in Jira and "First Last" (in quotes) is the user's first and last name.

According to both release notes for cloud and the cloud documentation this is implemented. However, it is not working and Atlassian Support suggested I vote for this feature.

Release notes: https://confluence.atlassian.com/cloud/blog/2019/12/atlassian-cloud-changes-dec-23-to-dec-30-2019

Documentation: https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-functions-reference-764478342.html#Advancedsearching-functionsreference-updatedByupdatedBy()

Why is this still not implemented? What is the use case that Jira server users would want this, but not cloud? Please get this in. 

Now that this specific functionality is being added to Jira Server 8.0 (as mentioned in ticket https://jira.atlassian.com/browse/JRASERVER-1973), when can we expect the status of this request for CLOUD to change and no longer be "unfortunately we don't have any plans to support this in JIRA for the foreseeable future"?

I am very eager to see how rapidly something added for Jira Server gets added for Jira Cloud to reinforce to your cloud customers that Jira Cloud is not 'Jira Lite' or a second-tier product offering.

Looking forward to having this functionality in Jira Cloud!

Agree 100% with Gregory 👆🏼

This seems like it should be a standard feature with Jira and not something I would need to purchase an add-on to achieve. It also seems odd they would agree to do it for the server version but not the cloud version. Why is that the case?

Give it another 15 years.

I've noticed that the same request for the server instance is now being picked up to be developed. https://jira.atlassian.com/browse/JRASERVER-1973

Could this be done for cloud too?

Any chance that this can be implemented out of the box in JIRA?

Another version of this request: https://jira.atlassian.com/browse/JRACLOUD-15235

Seeing as how there is still a demand for this issue I would be interested in seeing this issue revisited or, given the explanation in the description, closed. 

I would be interested in the reply as we are self-hosted

not available for self-hosted server solutions .. I'll ping the developer

This feature is implemented in JQL Search Extensions for JIRA. It's very easy to use and your JQL looks like updatedBy="John Smith"

+1 to this feature, before this feature request is going to have a bar mitzva

Actually...tap the RSS feed and parse the XML...and you can make your own table.  If I have time, I'll whip something up...

george.bachrach1528236645 That's very useful, thank you.  And while there's no date column, the date is underneath (in the JIRA interpreted date format...  )

That's at least something. Nice thinking.

So I managed some sort of workaround without using a plugin. I created a dashboard with the gadget "activity stream" and set the global filter on that to my username. It shows everything I've created,commented or edited. However there's no date column...but it's automatically sorted on latest.

I concur. This shouldn't require a plugin. 

+1 vote. This is simple request but would save quite a bit of time.

Please add this BASIC functionality, it would save me so much time If I could see all the issues I've updated. After using JIRA for a couple of years I can safely say that a big portion of the issues that I've been involved in, have not been assigned or created by me. The "updated by" issues are equally important. This is how it typically works:

• Person A creates a ticket and assigns it to person B. Me, person C, add a specification to it.
• Person A creates a ticket and assigns it to person B. Me, person C, add something to the description.
• Person A creates a ticket and assigns it to person B. Me, person C, add a comment.

I would add that this is not basic scrum functionality, but basic system... Just about any system has created by, modified by fields for audit. 

This needs to be baked the core in and not pushed to an add-on.

Can the title of this ticket please be updated to:

"Support basic Scrum functionality, like - Tell me what you worked on yesterday"?

A paid-for add-on is not a solution.

Also, it's not enough to know that someone updated an issue. We need to be able to put a date range - find all issues updated by user between X and Y dates.

Hi all, Automation for JIRA may be able to help out on this issue and is a solution that can work both in cloud and server.

To achieve this, add a multi-user custom field called: "Updated By". Then using Automation for JIRA add a rule that adds a user to this field every time it is edited.

You rule would look something like:

It is then pretty trivial to search by this. It can't do what field was updated or when, but it is a step forward.

@Nick - with you 100% on everything you said above. The fallout from that was on another level.

@Warren - have you checked the Watchers area on this issue: if the hyperlink says "Stop watching this issue" then you are watching it. If it does say that, click it and it will toggle it to "Start watching this issue". Flaming is not my intention on any of the tickets that you perceive I/we are 'ranting' on.

Speaking for myself only here, I have been getting increasingly frustrated by the lack of very basic features that Atlassian are happy to have plugged by third party software....which is [almost] tolerable if you're not using the Cloud (it still shouldn't be necessary to have to use them - they should be there OOB but at least it would 'fix' the problem). Nick is completely accurate in my opinion when he states "I don’t think the discontent of the user base is going to be going down on its own without addressing these high voted basic functionality issues, or much better communication, OPEN communication, for WHY these are not being worked on. Without those I’d guess that the frustration will boil over more frequently."

Atlassian do themselves no favours by trying to get people like myself and other 'ranters' to take the matter offline (as I have seen Dave trying to do on other 'basic feature lacking' tickets I am watching). The very reason people are watching these tickets is because they want to be kept updated. I actually feel desperately sorry for Dave Meyer (it's not the first time we have crossed paths in a similar fashion over the lack of fundamental features with open tickets over a decade old in the making) - he is facing the brunt of vexed users while someone higher up the chain (I would assume) is prioritising ridiculous changes like moving UI elements for no apparent reason (the latest one has just confused a whole bunch of my users) and making nice rounded corners on the interface. I'd happily forgo any such 'bells and whistles' for the next decade in favour of having the important things addressed that are making my life as a JIRA admin an increasing headache to the point where I have to advise my employer that we need to look at moving off it. My employer looks at me like I've announced the Earth is flat when I say that I have to give someone 'God' access to the entire system if all they want to be able to do is create their own project for their team, for example. Other times they, like I, simply don't understand why our Team Leads can't see who in their team last updated a ticket since, as pointed out, this is just a very basic necessity for a DMS. I've used all manner of DMS systems over the many years I've been in QA and JIRA is the only one that lacks it [along with a whole bunch of other core features of central importance].

Why did we choose JIRA then? Simple, and observed by Nick, above, low-cost. The bean counters fail to realise that there is a very definite trade-off between low-cost and functional. I advised them to buy the hosted version, which I have also used historically, but was told [paraphrased] "Cloud is where it's at these days, we'll have that; and it's cheap!" - ignoring the fact that I pointed out we'd be limited WRT plugins, wouldn't be able to do custom scripting and so forth, and that it would (and now is) costing is more long term. It's a false economy. What do I know though, right? I'm just the guy that has to do the admin. Meh

@warren - Sorry for adding to your inbox, but with the posts of the past few days I feel I need to provide an alternate perspective.

The fact of the matter is that there are features that honestly should be available by default that Atlasssian appears to have left to add-on developers to serve. This doesn’t help those of us using the OnDemand service where these add-ons are not available. In general, many of us have dealt with these missing features as a tack-on cost of running a low cost service. i.e. Less out of the pocket, more time invested to keep things running. This results in a general undercurrent of frustration and dissatisfaction. Then, when we see motion on issues we don’t care about, apparent dismissal of things we do care about, and features we like either being removed or broken*, it wears on our patience and brings that frustration more to the surface, which is what is happening here.

I don’t think the discontent of the user base is going to be going down on its own without addressing these high voted basic functionality issues, or much better communication, OPEN communication, for WHY these are not being worked on. Without those I’d guess that the frustration will boil over more frequently.

*One big example of breaking a feature is the user management debacle from 2014. If you weren’t around at the time, user management had been changed from entering username, email, and first/last name to just entering the email. Domain was dropped to create the username. If, however, you had the same email for users on different domains (user@gmail.com vs user@yahoo.com) the name was dropped entirely and the username became U# where # was the total user count they were. When I wrote in about this I was told “they can’t test every edge case”, which was just insulting to me. I’m in QA and I know what’s an edge case and what’s an obvious error. This simply was NOT tested before going live. There were also issues of this not being announced, and very poor methodology of user testing and it was an absolute mess. If you want to look it up, the issue is here: ID-75

Yes that is very useful, thanks for the update CSaxon.

Why does it seem Warren's account was just created 3 hours ago?

reporter = warren.goldman1482687766 and Zero issues reported?
watcher = warren.goldman1482687766 and Zero issues found?

Hmm, nice try ....but I'm not buying what your selling

I am not watching the issue, but still get the emails, wish there was a way to stop them. Issue is 13 years old, and all recent comments are not helping me with the issue, just rants.

Allot of great points here. I hope someone is listening. I'd really hate to port to a new solution just because customers aren't being heard. There are features which I really like, but that lack of some are crippling! Can't justify 3rd party agreements and deal with legal (for enterprises that require this level of rigor) just to install a small bit of functionality that otherwise should be OOB. It's painful...

Help us Atlassian!

@Greg @Nick: Yes, you'd think the whole point of watching the issue would be to get updated about developments (or, in this case, the lack thereof). I suspect the difference here is that we are thinking and Atlassian are not. Dave has tried on other issues I'm watching to get a contentious commenter to go 'offline' with the discussion with similar results. Atlassian have, insofar as my experience goes, zero idea what transparency actually means despite their assertions to the contrary. They like to put a link into such topics as this indicating what steers their decision-making processes when the thread gets heated with regards to feature requests (however basic and needed) and improvements but apparently paying customers near-screaming for it and rinsing Atlassian for ignoring such basic features for over a decade with hundreds of watchers and voters isn't one of those criteria. I suspect this will fall quiet again for another few years before whichever incumbent wearing the Product Manager hat at that time decides to do the ubiquitous cut 'n' paste update I mentioned before. I think, as per Tushar's earlier recommendation, that TFS is the way forward for us here. Probably not an option for everyone however

It seems that Dave doesn't understand his own product. We are watching this issue so that we DO receive email updates of everything relevant to this issue. One of which being Atlassian product managers bothering to get off their ass and do something about this issue.

Truly Dave, if you want to avoid sending email updates to all the 237 watchers on this issue when you leave a comment, the best thing you could do is GET THIS IMPLEMENTED, then there won't be anything for us to watch and receive emails from!

@gary - Thanks for sharing. I for one do want to receive that email notification so I can follow the developments on this issue. Seems to me that's the whole point of watching an issue.

A further update for those voting and watching this issue...

Dave Meyer, that's very altruistic of you but do you not consider that the other watchers would want to hear what you have to say? I'd aver that they love to hear your explanation on behalf of Atlassian as to why this and other much needed features are over 10 years old on the 'Ignored Elsewhere' list. Just saying.

Just to update this ticket... I received this from Dave Meyer earlier after my comment above.

Dave Meyer, I think it is vitally important for Atlassian to be transparent and not take these things 'offline'. For the avoidance of doubt, and in case it wasn't obvious (it should be), it's not just me that's frustrated...or didn't you read all the other 100+ comments on this ticket and the others I mentioned or the ones on the link posted by Philip Schlesinger?

Dave Meyer: Please keep these discussions public - I don't want a call because then all the information is lost on this thread.

My organisation need this as well. I would put precisely zero faith in anything Dave Meyer or any other Atlassian representative says even if they said they were delivering this next week. This has been open over 10 years along with a bunch of other standard feature that should be offered 'out of the box' by a supposed enterprise DMS.

My company is still looking at alternatives because, as noted by Tushar Mhatre, Laura McKevitt, Brian Jackson, Greg Hoggarth and Philip Schlesinger (and numerous others) above, JIRA doesn't care about delivering basic and needed functionality to its paying customer base, that much is self evident from the link posted by Philip Schlesinger, above. Instead it's content to take our money and deliver a pretty UI instead (which, incidentally, is becoming more confusing when they move UI elements around on a whim and repeatedly show me a 'bubble' to highlight where it's moved to this time around. When I click the nagging Got it button it shows me it again countless times!).

It's like this little gem of a bug that forces the JIRA admin to compromises the entire DMS system due to woefully inadequate security permissions. I've been waiting for that one for ages and that, too, has been open well over ten years. It's directly related to this one, which Atlassian saw fit close(!!!) as 'Tracked Elsewhere' (which I would suggest is metaspeak for 'Ignored Elsewhere'). And then there's this one that is massively annoying as well that I got one of the staffers at Atlassian to raise - constantly nagging me to re-index. If I wanted to do that myself and get harassed all the time about it I'd have used the On Premise version and not assumed that this would be taken care of by Atlassian and their Cloud system.

Never mind about delivering useful stuff like this though, hey, Atlassian - keep the populous on its toes with pointless and unnecessary UI move-arounds. Well done you. You're are categorically losing customers due to your utter contempt for them and their fundamental requirements. Pay attention to us - we pay your wages!

As for Dave Meyer's comment: "...As noted in the comments, there are several add-ons that support this function for JIRA Server. We are working with these partners to bring support to JIRA Cloud ASAP..." - well, quite: nice if you're using On Premise but zero help if you're using Cloud. This basic functionality oversight should not need plugging with third party tools. And as for "...We are working with these partners to bring support to JIRA Cloud ASAP..." - another 10 years for a further "...Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience..." cut 'n' paste update then, huh, Dave Meyer? Or perhaps Atlassian will close this as well as 'Ignored Tracked Elsewhere', hoping that users will get so tired of clicking through the links to try and find the actual current open ticket and give up?

A day in the life of an Atlassian Scrum

• This issue: 465 Votes and 241 Watchers. Outcome: Over 10 years later, not implemented. "Dave, please cut 'n' paste the usual 'Thanks for voting and commenting on this issue...' etc text to keep the plebs happy would you?"
• Next issue: "I'd like to see an animated smiley face and hear an MP3 fanfare every time I raise a new bug please." 0 Votes and 0 Watchers. Outcome: "This is genius! I want all current sprints put on hold and everyone working overtime around the clock until this amazing, value-added feature is implemented! Go, team, go!!!"

(＾＾)ｂ to Greg for pointing that out.  Anybody else want to see the list of unresolved JIRA/JIRA Core tickets sorted by votes descending?

https://jira.atlassian.com/issues/?jql=resolution%20%3D%20Unresolved%20and%20project%20%3D%20%22JIRA%20(including%20JIRA%20Core)%22%20order%20by%20votes%20desc

Atlassian don't seem interested in making Jira the pre-eminent enterprise bug-tracking tool, which is a pity because it could easily be, if they just addressed the top 20 voted items instead of wasting time making the UI more pretty. The UI is good enough already, they should focus their time on what actually matters to their paying customers.

"What did I do over the past two weeks?" feels like the first question most users would ask of any task management system. I don't follow how this is still not an available search criteria in JIRA, and I'm baffled that the response from Dave Meyer of Atlassian is what it is.

I agree with previous poster, considering ridding ourselves of JIRA if they fail to support the basics such as this request.

We switched to Microsoft TFS for one project and I am a much happy camper!!!! Does not look like JIRA team cares about its users.

I also would like to see this functionality built into core JIRA please.

I found a link once here on this boards, with a summary of the items that Atlassian hasn't been able to implement yet in the past 10 years (like this one here). Anyone has the link maybe? Cheers in in advance!