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...

This should be a basic function of JIRA, rather than a function for sale!

I seriously have a love and hate relationship with JIRA.  It's a robust tool that i've grown love to discover the potentials for our business AND hate at the same time because it lacks so many basic functionalities that are not important enough to be "on your current roadmap".

Want to rename a group?  Better make sure you craft its name for business use for the next 10 years!
Want to exclude Weekends with JQL?  Better make sure you spend more money on other add ons!
Want to show Epic > Story > Task > Sub-Task relationship?  Better make sure you know that can't and be ready to do manual work!

Please get your priorities straight.  You've made a lot of improvements over the past years but the lack of BASIC functionalities is really what's frustrating your customers.

This story has been open for 14 years. If you're expecting any resolution in the next 5 years, then you're going to be disappointed. Get used to it, because this is how Atlassian treat JIRA and their JIRA users.

If this lack of support is a problem for you, I suggest you migrate your company to use a different tool, before you begin to rely on JIRA too much and it becomes too costly to move away from.

As many companies are held to several Security standards this is a real need for reporting and auditing

I read all comments and I am on position that this should be implemented asap. Reason is pretty simple - this should be a basic functionality to be able to find out list of the issues modified by specific user. This information is kind of available in 'Activity > All' for particular issue which mean that it is stored in db and therefore implementation shouldn't be so complex - this is another point for 'yes' lets do it.

Hi, our plugin is now also available for the self-hosted server version: JQL Search Extensions for JIRA

Full documentation of the features is here

For example to find issues updated by a particular user you can use the following JQL:
issue in updatedByUser("helen", "daniel")

Enjoy!

@chris - I agree, but from the history it appears that this logic goes against the Atlassian business model.  Provide a platform that is superficially functional and cheap to license, and leave up any improvements or extensions of functionality to third parties who charge, and Atlassian takes a share of that transaction. It's crowd-sourced development.

Clients shouldn't rely on 3rd party add-ons (that cost money) to deliver functionality your product should provide inherently.

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!

This is a very basic feature. Searching by "who" updated something is in just about every system. To point people to plugins is not the right way to do business. You should reconsider this specific issue. I understand some issues being solved by 3rd party plugins, but not something this basic.

"Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience."
Is that why you have a 12 year old issue with 100 comments unresolved ?

Open for 10 years? REALLY?!

Am on JIRA Cloud, can't install ScriptRunner. Amazed that this is not out-of-the-box functionality in JIRA.

plus 1

I have seen quite a lot of improvements lately (Jira Cloud), so am hoping for that one too. cheers

edit: @Dave: You mention some add ons that provide that feature. also, in the comments some tips are mentioned. would be beneficial if you update your original comment to include these (tips and add ons), so your clients don't have to sift through 100 comments.

I've added my vote in favor of this enhancement. Like others, I feel it would be very useful (for example, I needed a list of who had changed which issues in the last 24 hours). I hope you'll reconsider the decision to close this request.

One of our projects shifted to Microsoft (TFS). So glad about it..... Now I can do the queries I need. Microsoft is now capable to doing everything that we need, all in one place - Requirements, Test Cases, Bugs. Of course our development platform is Visual Studio, so that makes it even better. So much for having to put up with Jira not making such small but very useful updates for over a decade....what a shame!

I agree with the request. As a side note to what others are mentioning (which I agree with) I need to know if I have internal personnel that are making changes that do not follow our processes, etc. So if they change something that is impactful to our workload and they continue to do so, I would have no way to know who to train or discuss this with. We also are working to make this tool an enterprise tool and this would be an issue for a large portion of our organization. I also agree that there is no impact to UI if we add it as an optional column but not default the UI to show this information.

Dave, if you think your PR platitudes for why you aren't implementing simple and very useful features such as this is:
1. Helping any of your paying customers use Jira in their workplace
2. Building goodwill with your paying customers

Then you are in dreamland.

Dave,

I completely agree with Crates. This feature is easy to implement, needed by lot of paying customer to improve work efficiency, is provided by competitors and something a product should have had in the first place. I don't see a reason for not implementing this. Once implemented, I don't see a cost to support it unless there is a defect. I small fix that will address lot of customer's problem should get priority. Think of the cost of losing existing customers to your competition. Half my organization (80 K+ employees worldwide) uses Microsoft technologies and half uses Jira. Going forward, we would want to consolidate to a single tool. Issues like this do not make Jira favorable for us.

DMeyer:

Adding a column to the list of available columns by which to sort and filter, not selected or visible by default, hardly seems to have an impact on the weight or "clutter" of the UI. In fact, when not selected, it adds zero weight to the UI; it simply doesn't appear at all, as the list of available criteria already out there by which to filter and search issues is long enough that they don't all display at once anyways.

It may be simply an issue of perspective or semantics, but saying "we don't have any plans to support this in JIRA for the foreseeable future" sounds an awful lot like a blanket refusal to me... and frankly, I don't know which is worse: saying no and closing the ticket, or saying no and keeping the ticket open for a decade despite hundreds of people requesting the feature.

Moreover, I'd be willing to wager your developers have invested some time into at least a few features that were requested by less than 369 paying customers over the course of twelve and a half years. Dress it up however you like... this is a feature that is massively in-demand, is not available to your Cloud customers presently via ANY means, and could probably be built in a couple of hours. It's an added SQL constraint, not a complete UI overhaul or some flashy new feature entirely outside the realm of what you're already doing.

Hi Dave,

This is not a completely new feature. Jira already provides JQL. This is a much needed enhancement to JQL that is needed, without which our productivity in tracking work is affected. This is something that competitive products have and is seen by my organization as a major weakness of Jira. How can a product that provides version control not provide a mechanism to track changes made by a user? That is something very basic that should be included in the product instead of waiting on 3rd party to provide it using your API. I understand that this request has been pending for over a decade. That shows how much Jira product management cares about voice of customer and user productivity.

Hi crates.mcdade,

It's not a blanket refusal – if it were, we would close the feature request entirely and say so. Our intent is to be open and honest about our intentions, and that includes a realistic assessment of how far we can look into the future. We review all the feature requests on jira.atlassian.com and continuously update our roadmap. We are saying that we are not currently working on it and it's not in our immediate plans; it's not a question of the value of the feature, just a matter of prioritizing the hundreds of feature requests (and vast amount of work like performance, security, new user onboarding, and UI improvements that don't get captured here).

The APIs for building an add-on to do this in JIRA Cloud are available, unfortunately it doesn't look like any add-ons have developed support for this yet. Typically the reason why something that may be available in a plugin isn't part of the core product stems from the following:

• Additional support, testing, and ongoing maintenance costs of adding the new feature
• The quality bar we set (anything in JIRA needs to be guaranteed to work across every supported platform, and at massive scale in a performant manner)
• The fact that with every feature we add any customer who does not need that feature is going to perceive it as "clutter" in the UI, so we need to make sure the benefits for customers outweigh the added complexity

dmeyer:
Thanks for the feedback, Dave. Which add-on(s) can I use on my JIRA Cloud instance hosted at Atlassian to support this feature?

Also, with nearly 400 people requesting this feature over the last decade, why the blanket refusal to incorporate it into a future version of the software? I can understand it not being a priority, but why not at least include it in the roadmap? Obviously it's doable if plug-ins have incorporated it.

I may have to have a word with your development leads at this year's Symposium.

Hi everyone,

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. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future. As noted in the comments, there are several add-ons that support this function.

Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

Hi all,

Enhancer Plugin for JIRA has similar reports and gadgets.
You can get report or add gadget to see users/groups activity according to your favorite filter and time period.
We also plan to add jql functions as well.

A column in the search interface for sorting purposes would also be appreciated.

Could really use a feature like this. Come on JIRA dev team...

It's been open for 12 years, so I don't expect a resolution in the next 5 months is likely...

Looking to scale JIRA use across several global teams. Can this be figured out and implemented by March 2016?
Thanks very much.

Would someone in Atlassian please suggest a SQL query that would answer the basic question of "show me a list of all JIRA issues which have been either (a) commented on, (b) edited by, or (c) transitioned by username 'XYZ' within the time period of 'Y1/M1/D1' and 'Y2/M2/D2'"?

Yes, there is. "Never".

So is there an ETA to add this feature? This is a basic feature that all other competing products offer.

"At this time, this suggestion is not on the JIRA development roadmap. ... I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions."

Request Created in 2003, 323 votes and counting ...
This information; "last update by" while seemingly trivial, is very valuable. For Small teams, maybe this isn't such a big issues, but when you have 7+ projects across 5+ distributed teams it really is a nightmare to obtain the much needed information and analytics out of JIRA and a major driver for our organization to start evaluating different solutions

+20,000 for this feature

It is a nightmare and a big waste of time trying to find something simple as "Issues updated by a particular user". Why can't Jira team provide this feature to make users more productive? It may just be that others are just working around it and wasting lot of time to find this information, but have not logged or searched for this issue yet. I am highly disappointed! Would consider going to TFS that we used for another project.

hurry...Atlassian should fix it

+1 for interest on this feature

No.

Are we ever going to get this feature??

shame

This is one of the features almost every mature Issue Tracker system has. The ability to filter for something like "affected by me" to see only issues you are involved is very helpful to track the progress of the issues one reported or commented on or resolved and waits for QA. This is the scope of real work for the person and adding a field into the schema for such a purpose is the reasonable trade off I believe.

I believe the information is simply not stored anywhere so cannot be returned by a query.
They'd have to extend the issue schemas to include that piece of information and that's not something they want to spend resources on at the moment.

Nope; see the Description.

Any chance this is ever going to be considered as we really need a way to report on who updated the issue, rather than just the assigned user

I just tested, and the JIRA Toolkit plugin DOES work for the following in our environment:
*edited / changed a value on an issue
*transitioned an issue

I'd like to see this. The JIRA Toolkit plugin only will find participation if the specified user is:

• the reporter
• the assignee
• commented on a specific issue

The JIRA Toolkit plugin won't detect situations such as:

• edited / changed a value on an issue
• transitioned an issue
• created a review in Crucible for an issue
• committed code towards an issue

I would probably create a new dashboard just for this monitoring purpose so it's not taking up space on your main dashboard and utilize the Activity Stream gadget twice (use the 2 column dashboard layout), so you have the two users in their own columns. Does that make sense? Again, not ideal, but it should work as a workaround as you're only needing to monitor two users at this time.

thanks for the reply but in activity stream how can i get two people together as I see it only for one employee at a time ... also i am not able to strech or expand the gadgets and they are occupying lots of space with in the Dash Board

@Kishore – I know it's not ideal as it's not query form, but you could create a dashboard for this using the Activity Stream gadget and filter it by the two employee's usernames.

hi i need to know the JIRA participation of two employees in my organization for what ever they change
please can you give me JQL

I just messaged the CEO's asking if we could get some progress here: https://www.atlassian.com/company/contact/contact-ceos

This is why I have decided to build my own open source PHP/Mongo/MySQl/Elasticsearch based project and ticket management system. Its extreme but if Atlassian come complete their solution and fulfil their customers needs I have no choice, can't keep limiting my business because of Atlassian.

This is not a joke. This is the way that Atlassian product chiefs show how they care about their customers! This is almost a message to all of us from them saying: "We don't care about your needs! This product is ours and we'll do whatever we want with it!"

This is a joke. This issue is almost 12 years old!

Atlassian, sort this out! You're letting down so many paying customers!

Up! this feature is really important for us. We need it ASAP.

I do need this feature right now

Will we get this feature implemented some day? how many votes are necessary to have some serious attention on this?

terrible !!! very simple feature and it is still outstanding

shame!

I see this issue is 12 years old Is there any plan for it to be addressed? Trying to see what my team have been doing is really hard work otherwise.

@Jason Brison The filter is just a workaround since "Updated By.." feature is not available. you may only use "assignee changed by (<Person X>)", "resolution changed by (<Person X>)", or "priority changed by (<Person X>)" for specific purpose. that's all this workaround can do.

jaclyn.liu, Even with the added JQL, that query ONLY works if I've changed the status. If I have never changed the status on the issue, your query isn't going to catch it.

@Jason Brison please try this one: "status changed by (<person x>) AND updateddate > startOfDay(0)". it should give you the issues person X updated today.