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!

funny that it takes ten years to do this and still the version does not do the most basic thing that is to get the updatedBy the currentUser()... why else would people need this? be smarter.

it really is amazing my company pays for this software, and we are definitely not the only ones.

10 years to build a feature and still not even the most basic use case is properly implemented.

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?

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.