nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Random user assigned to ticket

Joseph Jong

There are 3 JIRA tickets in our sprint backlog that have been assigned to a name "Ehemaliger Benutzer" who has never been part of our account.

Have also checked history and nothing is obvious on how the user name got assigned.

Flagging as potential security concern.

Accepted answers

Jack Brickey

Have you deactivated the user account? Have you queried for all issues assigned to, watcher, reporter = EB to better understand the history?

All comments

Jack Brickey

Have you deactivated the user account? Have you queried for all issues assigned to, watcher, reporter = EB to better understand the history?

Joseph Jong

Thanks.

I'm admin for the account and most projects and this user is a ghost. Has never been added as a genuine user in the first place.

Just wondering if anyone else has observed this. Could this be an internal Atlassian Employee?

I can simply reassign and would assume the user would simply disappear, but thought I'd raise for discussion.

Jack Brickey

I have never experienced. I would inspect the user closely. What is the email associated? Is it associated with your company’s domain or something else?

Nic Brough -Adaptavist-

There is no way to have an assignee that is not a valid Jira account. One of your admins created EB, or allowed self-sign-up so they created it themselves. You'll need to talk to all your administrators.

Atlassian don't add named accounts when doing support work, they use the built-in admin account.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud