Jira catfishing?

[Peter McNeil]

Yesterday during sprint planning I assigned several stories to myself then received notifications from Jira saying that my colleague Chris assigned those stories to me.

Chris had not assigned them.

So this would be funny and a bit of a so what moment, but I've been involved with many clients who are interested in auditing systems and knowing who changed what is kinda important.

Has anyone else seen this? I am a customer so tried to log a bug, but I couldn't add a ticket against Jira cloud (maybe the AI has taken over).

[Darryl St_ Pierre]

I was looking into something similar recently. The answer I arrived at is this is a known bug having to do with permissions at various levels and actions that is mentioned on one of the other responses here. My browser history shows this link: [JRACLOUD-80541] In site-level audit logs some actions are attributed to Author : JIRA despite having been enacted by a user - Create and track feature requests for Atlassian products., though I'm sure one item I read was more specific to the scenario.

[Peter McNeil]

Thanks for that Darryl.

That looks similar to the issue here. This is a jira action that is attributed to a different user, not the creator of the issue, just a team member.

The bug link is kinda worrying due to the fact they say "the Audit logging system is complicated". Who created a comment or made a change should be a really basic thing, either recorded directly in a log as it is done or in the record itself. Account Ids are unique and should be available at the time the change is made (otherwise how do you enforce security) so if grabbing an audit log is getting complex they do need to refactor (IMHO).

[Brita Moorus]

Hi, @Peter McNeil!

Did you also check the history under work items to ensure that your colleague Chris did not assign them to you?

Sometimes Jira automations or workflow post-functions can automatically assign issues during creation or transition, and they often log as “assigned by system,” but notifications may attribute it to the current user - for example, your colleague Chris.

If you're on a supported plan, ask your admin to check Settings → System → Audit Log for the specific issue event. Also check your project’s default assignee settings, component assignments, and automation rules.

That should help you pin down whether it’s a workflow rule, automation, or some default configuration quietly assigning the issue.

Hope this helps! ✨

[Peter McNeil]

Thanks @Brita Moorus As a bit of background I've worked with Jira for a good number of years, I used to work for Atlassian.

The history does say that Chris assigned it to me, however it wasn't him, it was me. I was on a call with Chris at the time, I was running the sprint planning and doing all the things :-)

The default is unassigned, that was why I was assigning it. I'm the admin.

Audit log only shows that I updated the sprint, nothing more.

The fact that Chris and I were looking at the sprint at the same time is the only co-incidence. 

Definitely not a workflow rule or automation or default (note: team managed project).

And I checked with Chris, he didn't do it :-)