Reassignment for a bunch of tickets

[Jon Kocen]

Today, we had over 360 tickets get reassigned to a user, one right after the other. This was across multiple projects and ticket status's.

However, no one actively reassigned the tickets. This seemed to happen on its own. There is nothing pointing to someone running a bulk update or any other activity in the various logs > access_log.2020-05-06 or atlassian-jira.log, catalina.out

All of these tickets were assigned to one person and we don't know how. Any suggestions on where to look to figure out why this happened and how could it happen.

Thanks

J.

[John Funk]

Hi Jon,

When you look in the history of one of the tickets, who does it say changed the name of the Assignee?

[Jon Kocen]

The history shows the person's name, avatar, the current date/time of the change. Just like if she had done it herself.

[John Funk]

Are there other history items that happened at the same time? 

[Jon Kocen]

No, just the assignment to this one person. There are closed and open tickets that this happened to. I can't find any pattern with the tickets - open, closed, old, new - doesn't seem to matter.

[John Funk]

Is it the same person's name in the history for each card? 

Not sure that log activity would show Bulk changes of issues

If it's the same person, I think you have found the culprit.  ;-)

[Jon Kocen]

Yes, it is the same person on all of the tickets. I did find some bulk edits in the log but the user doesn't have rights to perform bulk edits. This is limited to Admins.

The user said she wasn't even in JIRA at the time, she was doing a security scan on one of our custom applications. 

I will do a simple bulk edit today and see how the log captures it and then I can see how the other bulk edits under this user's ID look like. If they are similar then I at least know what mechanism was used to make the changes, even if I don't know how it got kicked off