Hi ayakovlev@atlassian.com , agree to former comments. This is far more a QA hygiene topic than a feature request.

Question: how many votes of user feedback is necessary? 759 for now seems a pretty high number. thx

Another dissapointing decision by Atlassian ^TM

I think I have lost the count already... that's too many basic features that they have 'decided not to proceed' with. At the same time, licence fees are higher every year, and the investment is harder to justify every year.

Might be looking for a replacement app in the future.

Hi Rudy Slaiby,

stating: "We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users "

and at the same time ignoring nearly 1000 votes on this issues for now over 17 years is a impudence!

Formerly one of Atlassian pillars was "Don't f..k the customer". This meanwhile seems to be reversed meanwhile by Atlassian!

To me this seems like another case of: Do not offer core features -> Thrive on plugin subscriptions.

This is an audit log flaw (could change a comment saying "im okay with it" to "over my dead body" without any trail other than "has been changed")

Todays decision by Atlassian to ignore this issue despite it being easy to fix is extremely disapointing.

Not to mention that this ticket has been open for 17 years and has the support of 759 voters (assuming an average licence of 1000 users, 759'000 users affected and 58-129Mn in licencing fees alone (software - JSM) + the cut Atlassian takes on marketplace plugins.

The literal billions of dollars spent by the 759 voters here over the last 17years should get us a developer for 3 days to add history to comments on Jira or Atlassian buying off one of the plugins that solves this audit trail issue and incoporating it.

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.

Jean-Pol Landrain added a comment - 19/May/2016 6:14 PM

Why the hell Atlassian doesn't understand this is both a penalty for existing customers and a blocking factor for potential new customers ? Guys, you are losing business. That's insane.

We are in 2024 and that's still not possible. This linked to new legal requirements, along with a new licensing model that forces us to move to the Cloud or to use more expensive Datacenter licences for our Atlassian products, are the main reasons you've lost a large european customer. We were using multiple instances of each of these products : Jira, Confluence, BitBucket, Fisheye/Crucible. We are currently in a migration process moving out of the Atlassian products. You've lost a long time customer, about 20 years. So good bye, Atlassian. It was a nice journey, we can only blame you for not listening to your customers anymore.

+1 

The edited comment is flagged with an "edited" tag, yet the History/Activity log fails to provide any details on the changes made. The sole evidence lies in the email notification indicating that the project admin conducted the edits.

This discrepancy raises significant concerns, as it jeopardizes the reliability of JIRA for maintaining an accurate audit trail or supporting any form of attestation. Is there a vital aspect I'm overlooking? Rather than a mere suggestion, this discrepancy appears to be a critical bug that demands urgent attention.

+1 for the ability to see the change history of edited comments

813cab5e75b8 I agree, it should. But it doesn't and never did and as you see how old the Issue is, it probalby never will... so why complaining. Hundreds of companies seemed to have found a way to handle it. The strategy of Atlassian is clear. They will only implement something, if it CVE relevant or a feature they can sell or make more money with. So the main focus of Atlassian is to improve the Add-On platform, because there they make the money. So if there will be no hack of a Addon vendor, there will never come a solution for it. At least not for self-hosted applications. So why spending time complaining about it? We even have older issue requests here with higher amount of votes... so the strategy of Atlassian should be clear. They don't care about their on-premise customers. They just care about the addon platform and cloud customers.