Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×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.
Thanks.
Chandra.
Most likely the user edited a comment, which doesn't leave an audit trail in the history.
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Thanks
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Petter,
How that could be possible on a single issue in a project???
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Petter,
I have checked with the user, there are no external imports and not even any REST APIs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Petter -
Do you have any other possible suggestions, please?
Thanks,
Sekhar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.