How can I find out who and when deleted an issue?

Avatar
Permanently deleted user
Created
Hello,

We are dealing with a situation of deleted issue in Youtrack. We had quite a few comments added to it by us and a client but then somebody has deleted it.

1. It would be extremely nice to be able to undelete it.
2. I searched all our log files back and forth and can't find a record about who and when deleted it.
3. I tried creating and deleting an issue and I can't even figure out in the logs how can I determine an issue is deleted. There is not obvious record staging "Issue X is deleted"

Votes

0

Share

6 comments
Avatar
Dmitry Krasilschikov
Created
1. The permission 'Delete issue' manages if user able or not to delete issues in project.
2&3. Try to find an entry "deleteIssue" in the youtrack.log file.
0
Avatar
Permanently deleted user
Created
I did revoke permission to delete issues. I left it only in limited roles.

Looking for "deleteIssue" I can see it only in notifications.log files. There is no record for the issue I'm looking for, though even though I kept all logs since we started working with Youtrack. Users may have removed email notifications and thus there would be no record of it in that log, wouldn't it?
0
Avatar
Dmitry Krasilschikov
Created
Actually I don't sure notifications.log can help. I've checked - if user deletes an issue by the command 'delete' the only common 'doSubmit' stores in logs.

But 'dele' (or 'del') command prefix also is stored in the youtrack.log as 'suggest command' REST call. You can try to find these strings.
0
Avatar
Permanently deleted user
Created
I don't think notifications.log can help either.

I reviewed youtrack.log for 'deleteIssue' and issueID and couldn't find a record for that issue deletion.

I then ran some tests, here are the results
  1. acc-104058 delete with command, Apply
  2. acc-104049 delete with command, Silently Apply
  3. acc-104059 delete from inside issue page

Extracts from the youtrack.log file
... youtrack.log 21 Jan 2014 16:20:50,537 INFO  [MainServlet    ] [eIds=FzP&noIssuesContext=false&command=del&caret=2] [mzarnitsa@kmionline.com@216.69.207.81] Start processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzP&noIssuesContext=false&command=del&caret=2 21 Jan 2014 16:20:50,668 INFO  [MainServlet    ] [eIds=FzP&noIssuesContext=false&command=del&caret=2] [mzarnitsa@kmionline.com@216.69.207.81] Finish processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzP&noIssuesContext=false&command=del&caret=2 in 131ms 21 Jan 2014 16:20:51,142 INFO  [MainServlet    ] [s=FzP&noIssuesContext=false&command=delete&caret=6] [mzarnitsa@kmionline.com@216.69.207.81] Start processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzP&noIssuesContext=false&command=delete&caret=6 21 Jan 2014 16:20:51,157 INFO  [MainServlet    ] [s=FzP&noIssuesContext=false&command=delete&caret=6] [mzarnitsa@kmionline.com@216.69.207.81] Finish processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzP&noIssuesContext=false&command=delete&caret=6 in 15ms ... ... 21 Jan 2014 16:22:09,943 INFO  [MainServlet    ] [zG&noIssuesContext=false&command=delete%20&caret=7] [mzarnitsa@kmionline.com@216.69.207.81] Start processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzG&noIssuesContext=false&command=delete%20&caret=7 21 Jan 2014 16:22:09,946 INFO  [MainServlet    ] [zG&noIssuesContext=false&command=delete%20&caret=7] [mzarnitsa@kmionline.com@216.69.207.81] Finish processing request /rest/command/underlineAndSuggestAndCommands?issueIds=FzG&noIssuesContext=false&command=delete%20&caret=7 in 4ms ... ... 21 Jan 2014 16:22:44,884 INFO  [MainServlet    ] [/_events?window_id=90 [l.I:methodCall_deleteIssue]] [mzarnitsa@kmionline.com@216.69.207.81] Start processing request /_events?window_id=90 [l.I:methodCall_deleteIssue] 21 Jan 2014 16:22:45,901 INFO  [TextIndexManager              ] [TextIndexManager    ] [] Text index transaction started 21 Jan 2014 16:22:45,905 INFO  [MainServlet    ] [/_events?window_id=90 [l.I:methodCall_deleteIssue]] [mzarnitsa@kmionline.com@216.69.207.81] Finish processing request /_events?window_id=90 [l.I:methodCall_deleteIssue] in 1021ms ...
All calls recorded differently based on the way how issue was deleted. None of these ways actually make a trail of what issue was deleted.

I'm not sure how one can audit this log. If someone deletes an issue, there is virtually no record of that. I hope this can be fixed soon.
0
Avatar
Dmitry Krasilschikov
Created
You can extract the author and IP of any request from logs. As you can see the author/IP of all of these requests is mzarnitsa@kmionline.com@216.69.207.81.

I've also created the request JT-23202.
0
Avatar
Permanently deleted user
Created
It's just in this case I know which issues I deleted. If I search through regular logs, some time back, I have no way of knowing if this record about issue I'm looking for or not.
Thanks
0

Please sign in to leave a comment.