Can I give permission to be @'ed but nothing else?

[NancyB455]

A Human Resources project wants to add a form for people to request a communication be sent to the whole building or company.  The HR staff want to be able to @ people to alert them of the ticket, but most people in the building can't see any HR tickets but those they are the reporter on.  Is there a permission level that allows a Core Project Team member the ability to @ someone which would give them the ability to see that particular ticket?  Thanks.

[NancyB455]

I see in my notification scheme that I should be able to add notifying a "custom field" and we have "request participant."  But I'd like to have the participant receive an email when they are added as the participant...is that considered an "update?"  So if I say On Issue Update send a notification, the participant should that I just added should get it?  Thanks.

[jira guy]

@NancyB455 We do something similar in our company. Download the watcher plugin from marketplace. You can then add create a new field of watcher type, then add that field to browse permission for project. 

[NancyB455]

ooOOoh.  I'll take a look at that.  Thanks.

[NancyB455]

There are actually several "watcher" plugins.  Are you referring to "Watcher Custom Field for Jira"?

Thanks.

[NancyB455]

Also, you said to "add that field to browse permission for project"...but they can't see any issues in the project except ones they are a watcher on?  Thanks again.

[Andrew Laden]

You want to look at "Issue Security Schemes"

Issue level security allows you to restrict on a per issue basis who can see the issue.

Normally, you can not add the built in "watcher" field to issue security. (Atlassian has said they are not going to allow this) But by using the Watcher Custom Field instead, you can get the same effect.

You create a scheme that you apply to a project. Within the scheme you can create different Issue security classes. For example, you can make one named "Public" that allows anyone to see, and then make a different one "Participants only" that only allows the reporter, assignee and watching users (using the watcher custom field). THere are other options.

Once you do that, anyone who has the "Set Issue level security" permission for the project can apply an issue security settting to any issue.

This would be the way to give all users browse access to a project but limit what issues they can see.

[Jack Brickey]

it sounds like you want to be able to dynamically give browse permission to an individual user only when they are @mentioned and only to the one issue. That is not possible.

[NancyB455]

Er, yeah.  That about sums it up.  Is there some other way to give an individual the ability to view that one issue?  Like add them as a Watcher or something more official than just @ mentioning them?

[Jack Brickey]

You can certainly add them as a watcher which will accomplish your goal. Now the user will still have browse permissions to other issues can could find/view them if the wished.