Low priority username leak?

Christopher Morton_o9fl7g

In JIRA, if you use the @ reference internal usernames, the names will often show the username to internal and friendly name to frontend users/customers (Typically first name or first name and last initial). If you type @InternalUser, you get John S. rather than john-admin, which is the user's JIRA login account. Suppose you are using the TEXT field and assume you will link an internal user (coworker). In that case, you can expose the internal object for that particular internal user/coworker using the following inputs in the TEXT MODE editor.

[ @InternalUser | https://somelink.com ]

What ends up happening is the username gets pulled in automatically via Jira @ lookup, then nested as string input into a URL link. The result is a bug as it does not print the friendly name when the link is rendered but the internal username. What do you guys think?

On another note, I needed help locating where to submit bugs to the Jira team.

Any help is appreciative, and thank you.

Chris

Jira v8.20.12

Dan Breyen

Hi @Christopher Morton welcome to the community!  Atlassian's jira site is at jira.atlassian.com

I took a quick look and didn't see anything that looked like this issue, but I may have missed it.

I'm on the cloud, so I can't test it, but it sounds like it could be an issue.

Hope that helps.