permission to view this issue

[Alexis]

Jira Server 7.5.0

I have specific project settings.

Users and roles

• Developer (jira-developers)
• User (jira-users)

Security Level private (Default)
Issue can be viewed by

• Reporter,
• Current assignee,
• Project Role Developer,
• User custom field value (Issue watchers),
• User custom field value (Approver)
• In Global Permissions, Browse Users: jira-users

Case 1: When i create an issue, i can add users to Issue watchers field

Case 2: When i edit this issue i see "Users do not have permission to view this issue: user.name"

How can I fix case 2 ?

[Nic Brough -Adaptavist-]

This is a slightly convoluted one, but the logic explains it when you think through the timing.

You can not add a user as a watcher on an issue they can not see.  That makes sense - it's pointless adding someone because they can't see the issue and hence won't be notified about it either.  There's no point watching things you can't see.

So, on the timing:

• When you create an issue, you're going from "no data" to "a whole issue".  As you've added watchers before committing the create, Jira gets an issue with watchers included.
• When you edit an issue, the issue has a set of watchers, who can see it because of your permission scheme.  But you can't add anyone who can't already see the issue because of the "can't add people who can't see it" rule.  When you're editing, it's too early in the process for the new watchers to be able to see it, so they end up blocked from being added.

The only way to fix this is to include all the people you might want to be watchers in the security level.

[Alexis]

The other way, is give permission to change Security level: from private to public to Reporter

and add to Security Level public USER (jira-users)

and after that:

1. Reporter can change issue security level from private to public

2. add watchers

3. change issue security level from public to private back

Kind of stupid solution.

But I don't know how to resolve such problem other way.

The main idea is:

1. Create project.

2. Project can see Reporter, Assignee, Developer (jira-developers)

3. All issues can see Developer (jira-developers) only.

4. issue1, can see:

• Reporter,
• Current assignee,
• Project Role Developer,
• User custom field value (Issue watchers),
• User custom field value (Approver)

5. all other issues are restricted to access for users, if user do not in any condition in step 4