Totally unacceptable! Polls are getting closed while the requests are totally legit - thats how Atlassian threat his paid customers.  Damn, thinking that we PAY for this....i will never recommand Atlassian in any way after that switch to the Cloud, you missed big time.

What a SHAME !

They just close a 17 yo ticket with 500+ upvotes, without even a valid reason.

Unfortunately like 2c914093cc71 said before, they ABSOLUTELY DON'T CARE about giving customers a finished product and the more it goes the more they abandon functionalities that should definitely be included in an issue tracking software to delegate them to third party developers making these BASIC functionalities PAID PLUGINS. Which leads to tons of "abandoned" tickets like this one was (it isn't anymore since they closed it with no fu*ks given so it's officially declined now), and that have gathered hundreds if not thousands of CUSTOMERS VOTES.

That truly leaves anyone wondering what is that Jira project made for ?? Why are we taking the time and effort to write tickets for improvements and give upvotes ? since they don't care about finishing their product, all they're looking at is how to max out their benefits as fast as possible (check the financial reports, it says a lot).

We got fooled so badly my friends...

00dbe60c55f0  So for you that's the "only drawback" ??
Lol ! Would'nt you happen to work for SaasJet ? xD
Because mate, the major drawback is that this is a PAID plugin, and not a cheap one, for 100 users you're looking at $150 a month and for a thousand users it is above $700. That's a real shame for such a simple feature, we have description history but no comments history I mean...

That doesn't suprise me tho as most of the features (actually all the ones i've looked up) have never been taken into consideration by Atlassian team, this Jira project is nothing but a joke, a facade to let people believe they actually care about customers feedbacks. 

The sad truth is I can't even count the number of tickets for very important yet simple features that have gathered the interest of hundreds of customers, and that have been opened for YEARS, some even approaching 2 DECADES !! And some without even the tiniest answer, if that isn't spitting at the customers' faces then I don't know what that is.

Check the financial reports and you'll see where their priorities are.

> Your feedback is invaluable in shaping and enhancing Jira for all users.

With all humble respect it is a true shame that it took 17 (in words: SEVENTEEN) years to make a decision and now leave your customers without a feature that is required for traceability and audit passing...  (or make them buy another extension...)

For now, this feature is available with Issue History for Jira. It tracks both updated and deleted comments. The only drawback is that you need to activate this option before it starts tracking comment changes.

https://saasjet.atlassian.net/wiki/spaces/IH/pages/3118825480/Tracking+comment+changes

This is a feature that is becoming more necessary as time goes on - are there any plans to implement?  You already carry out the exact same logging with the description field, so including the comments only makes logical sense.

It should not require the purchase of additional apps/add ons, and really ought to be an in-built feature

A quick google search indicates that Jira is a proprietary product developed by Atlassian that allows bug tracking, issue tracking.  

Except the historical tracking can be changed on a whim given that comments can be edited and no audit trail is available to show otherwise. 

The lack of an audit trail for edited comments is highly disappointing and is just one of the many reasons many enterprise operations are unable to leverage the Jira software in the way the Atlassian's Sales & Developers imagined. 

+1

This feature should be brought back. As its very essential to see Edit History for most companies including ours.

I'm a little shocked this isn't already addressed - - this could cause audit issues, analyst issues, as well as customer issues if we don't know the before and after on these edits.  I did see where turning off edits is a 'possibility'.

As already mentioned, as soon as the edition was available - why not keep the history for Audit purpose at least?
Someone can write anything, let say something bad to a customer and change it afterwards without being noticed.

This should be a core functionality and we shouldnt be expected to pay for any addon in this regards.
More and more i see addons made for functions that should be included in your own software and vote polls that stays forever opens : what an opportunity for all those product manager to comment and get some users to pay the bills.

I must say that Jira Cloud is nothing but completed - feels like a Beta at best with a Premium price.
Let's hope this history is coming sooner than ever.