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; } } }

What controls who I can @ in JSM?

Jim Stewart_9b1rk3

Our help desk likes to be able to add an internal comment on an issue for anyone in the company. However, when they @someone, it only brings up a limited subset of people, mostly agents, and things like Git integration for Jira. (?) What controls who they can make comments to? Some particular group membership?

Accepted answers

Alexandre de Sousa

Hi @Jim Stewart ,

Unfortunatelly you can't control who they can make comments to, you can just control who can mention someone in a comment.

But your situation seems to be caused either by a combination of *Browse users and groups* permission and *Browse project* permission or *Browse users and groups* and an *issue security level*.

The Browse users and groups is a global permission which allows, beyond other things, the users to mention @ someone in a comment, for example.

The Browse project permission is a permission which allows a user to navigate in a project.

Check if the users you or your partners desire to mention have the *Browse project permission* in the project you want to do this or if the ticket you are doing this isn't in an *issue security level* that the user isn't in.

I hope this can help you.

BR,

Alexandre de Sousa.

All comments

Alexandre de Sousa

Hi @Jim Stewart ,

Unfortunatelly you can't control who they can make comments to, you can just control who can mention someone in a comment.

But your situation seems to be caused either by a combination of *Browse users and groups* permission and *Browse project* permission or *Browse users and groups* and an *issue security level*.

The Browse users and groups is a global permission which allows, beyond other things, the users to mention @ someone in a comment, for example.

The Browse project permission is a permission which allows a user to navigate in a project.

I hope this can help you.

BR,

Alexandre de Sousa.

Jim Stewart_9b1rk3

Yes, I understand fully what you're saying in terms of permissions. I don't recall encountering 'issue security' before.

Nic Brough -Adaptavist-

Issue security allows you to secure individual issues in a more widely shared project, doesn't affect who can mention, but it will limit who can be mentioned - no point in mentioning someone who can't see the issue.

Jim Stewart_9b1rk3

It occurs to me that the "users they want to browse" aren't even necessarily Jira users as such. They could be anybody in the company up to and including the CEO. So is there a way to make that happen? Do we have to use licenses and create everyone in the company as some level of Jira user or in some group just so we can mention them? I suspect so but how to go about that?

Yatish Madhav

@Jim Stewart thank you for this post ... and @Alexandre de Sousa thank you for the reply. It helped.

I agree with @Nic Brough -Adaptavist- , the granularity of permissions is amazing and at the same time tricky to fathom

Thanks for this. it help me resolve a mention issue an internal customer raised.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management