Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Changes in the issue are not showing up in the history logs but the updated date is changed.

Hi All,

We are using Jira Software Server v7.11

We have an issue created in Jira basic software project on 10th Oct, 2019 and lastly updated on 21st Oct, 2019. But the updated field on the issue is showing 31st Oct, 2019 and no changes have been done to the issue and not even any changes, if done, have recorded in the activity log .

Could you guys help me in this why this has happened and where to fix this and find the changes that have been done, if any done.





2 answers

Most likely the user edited a comment, which doesn't leave an audit trail in the history.

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 05, 2019 • edited

Hello Sekhar,

Thank you for reaching out.

I understand that you have an issue that was lastly updated on 21st Oct, 2019, however, the updated field is telling that the issue was updated on 31st Oct, 2019. Is it correct?

By default, all the update activities performed on JIRA issues are registered under the history tab, at the bottom of the issue:

Screen Shot 2019-11-05 at 17.49.16.png

If the date of the latest activities under the history tab is not the same as the field, can you please provide us a screenshot with the latest activities you have under the history tab? P.S: Make sure to hide any sensitive information on the screenshot.

If both the history and updated field does not match, the only root cause I can think of is that the data was updated by a different import method (Like CSV or XML import), but I will further investigate it to check any other possibilities.

Let us know if you have any questions.

Hi Petter,

Thanks for the quick reply.

I knew about the History tab you are talking about, I rechecked there for several times and even tried some scripts to get the activity list of the issue, thinking some logs might deleted or hidden. But no use of anything.

Here I attach the screen shot of the issue for what I'm breaking my head. Please find the screenshot and help me out of this.





change not showing up in History log.PNG

Hi Petter,

Any updates ???

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 11, 2019

Hello Sekhar,

Sorry for my late response.

Analyzing the possibilities, I believe the only thing that could be causing this issue to be updated without leaving any details registered in the history tab is that someone might be importing those updates using an external source (CSV, XML, etc).

Can you please check with the users that are able to perform this change if that is the case? Or would it be a big number of users?

Additionally, is the same behavior happening for any other issues? Usually, imports from external sources only make sense when you need to update a big amount of issues.


How that could be possible on a single issue in a project???



I have checked with the user, there are no external imports and not even any REST APIs.

Hi Petter - 


Do you have any other possible suggestions, please?




Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 02, 2019

Hello Sekhar,

Sorry for my late response.

Unfortunately, I'm not aware of any other possibilities that might be caused the updated date to be changed without any logs for that particular issue.

That being said, I can create an internal ticket so our internal team can further investigate this in JIRA logs, however, I would like to confirm with if it would be relevant to have this information since it happened for just one issue and it will require a big amount of effort from your side to provide more logs and history information.

If this is indeed a big lack in your application and you still want to further investigate it, please let us know and we will proceed with the ticket creation.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events