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

Can't add watcher with issue security

Oleksii Okhmush

I have this security scheme:

1 level

Accesses:

Project Lead

Project roles (Administrator, Developers)

Current Assignee

Reporter

Watchers

Browse project permission: any loged in user

So users can open project but see issues only if they are assignee, reporter.

When i try to add watcher to issue i have an error:

The user "xxx" does not have permission to view this issue. This user will not be added to the watch list.

How can i add user to watcher so he could see issue?

Accepted answers

Thomas Deiler_db00h3

Dear @Oleksii Okhmush,

this is the normal behavior of Jira. You can assign, or add as watchers only if the user has access right to that particular issue. It does not make sense to sent the user a mail for an issue he/she cannot see.

But please tell me, what is the purpose of your request? Probably I can give you another hint.

So long

Thomas

All comments

Thomas Deiler_db00h3

Dear @Oleksii Okhmush,

But please tell me, what is the purpose of your request? Probably I can give you another hint.

So long

Thomas

Oleksii Okhmush

I need to share some requests with user, but without changing reporter or assignee. If i add user to issue seurity scheme, it will see all issues, and that is the problem. I think if i use several levels of security it could be done, but it must be only 1 level of security

Thomas Deiler_db00h3

Dear @Oleksii Okhmush,

you can do following:

create a custom field of type user picker (multiple users)
add this to the issues (add to screen) of your project
modify your security level (add this custom field to the level)

Now only issues are visible to those users without opening all for visibility. But you have to modify this custom field manually.

So long

Thomas

Oleksii Okhmush

Thanks a lot for advise!

David Yu

See https://jira.atlassian.com/browse/JRASERVER-5621 about this limitation.

I generally go with this solution:

1. Install the Watcher Field plugin. This will let you edit the list of Watchers vs. having another list of users to manage in addition to Watchers. This lets you put a CC: field in the Creation form of Jira itself so you can add watchers immediately.

2. Patch DefaultWatcherService canWatchIssue() to allow users to be added to an issue as a watcher. This lets users use the native watcher interface to add new watchers.

If you don't feel like patching, you can always put the Watcher field in your Edit screens. Watcher Field plugin lets you override the rules for security levels.

Thomas Deiler_db00h3

Dear @David Yu,

the solution with this plugin is fine - but you create another dependency to a 3rd party plugin that could get commercial in the future (have seen this behavior many times).

I always try to recommend solutions without extentions, if possible.

So long

Thomas

Yu Fei

Have the same problem.

Yes, the problem can be solved by adding a custom field.

But it will be very strange because this new custom field's function is just like the "watcher". Now I have two watcher fields, and only one of them can work with issue security.

And it is hardly make sure that every user will choose the right one.

Since the original "watcher" is much easier to use, and users are more familiar with it.

Thomas Deiler_db00h3

Dear @Yu Fei,

then you need to ask Atlassian to add your described funtionality to Jira. I recommend to open a suggestion. Probably a related issue already exists.

So long

Thomas

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

permission

security