You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Please tell where can I find a edited comment history?
What table contain this infromation?
Comments do not have a history. If you edit a comment, the old one is destroyed, you can't know what it was in Jira.
There is an open improvement issue logged with Atlassian to provide a comment history, but generally, I just turn off "edit comment" permission on systems where the history matters.
I'd argue that it is essential to keep it in the history - this is an issue tracker, you want to know what people have done with it.
Comments were tracked sometime between 2019 and about three weeks ago to where a deleted comment still displayed and edited comments showed the before and after comments. Not any more. This was essential in our business as approvals between dev and the client were managed, maintained in JIRA as the document of record. Now we have lost the history. :-( Please bring comment tracking retention back.
If you mean the comments from before they were edited, they aren't saved. Just like when you delete issues you can't recover them. In the related content someone has a plugin that saves them. I don't allow deleting issues or comments. They are historical data that may have been acted upon and you would want to know what that data is.
Since you're new:
Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.
Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.
The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.
It is not great. There is a request logged to cover maintaining a history of comments, but at present, most Jira admins simply remove the permission to edit comments as well as the delete permission.
@Chris Smith-Hill that does not sound like an ideal scenario at all. It would almost be worth removing those repeat-offenders' abilities to edit comments, so that they aren't messing with that data in post. I know I would be concerned if my QA were editing comments after the fact to hide that they didn't test something in the proper amount of time.