Hi,
Something very strange happened, history of a ticket clearly shows a specific time when I changed assignee to myself, I never opened the ticket..
Do I have ways to investigate this? Can I know how it was done? from which machine etc.?
Another possibility ... though you say you didn't view the issue, perhaps you did (possibly accidentally) and accidentally pressed the keyboard shortcut ("i", I think) for "assign to me". I've done that a couple of times.
That for sure can happen. Drives me nuts at times.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow, I didn't even know that exists!
That might be possible, if I randomly opened an issue while in my flow...
Thanks!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Couldn't find any automation or reason for this happening.
I guess this is the most useful and close to the root cause as I can get..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dani Koretsky - you can see all available keyboard shortcuts by pressing "?"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It could also be an automation rule that is set to run as your user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good point. Do I have a way to check those? to search and find such actions in automation such as "assign to user" ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That depends on whether you have an automation addon and if so which one. For example for Automation for Jira - project settings > Project Automation and inspect your rules
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dani,
Perhaps there was auto-assign on a component.
A component default assignee will override the project's overall default assignee.
Organizing work with components
Another common reason is a workflow post function assigned the issue to you during a transition:
"Assign the issue to the current user. Please note that the issue will only be assigned to the current user if the current user has the 'Assignable User' permission."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great idea, I checked.
I'd expect it would be with some changes made before or near that ticket history entry.
The previous change is 24+ hours before, and next change is 14 hours later..
Not transition or changes were made to the ticket around the time of this operation..
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.