Approvers continue to access the request if they are deleted.

[Tony Montana]

Hi!

When I remove a person from Approvers, that person still has access to the request. Why and how to stop it?

[John Funk]

Hi Viktar - Welcome to the Atlassian Community!

You need to look at the Permission Scheme associated with the project to see who can see issues. One thing to check is to see if the user was added as a Watcher to the issue. 

[Tony Montana]

@John Funkre-read

[John Funk]

Did you check all of those things?

[Tony Montana]

@John Funk RE-READ THE QUESTION, PLEASE!

[John Funk]

I can't help you if you don't respond to my suggestions. Your question: Why and how to stop it?

My answer: You need to look at the Permission Scheme associated with the project to see who can see issues. One thing to check is to see if the user was added as a Watcher to the issue. 

If the user can still see the issue, then they are associated with the issue in some way. 

[Tony Montana]

Facepalm. Leave, please

[John Funk]

Sorry for not completely understanding your question. Maybe someone will be able to help you better. 

[Tony Montana]

@John Funk 

We are using JIRA Service Desk 8.6.0. Now this is the behavior:
- Request not available for n-user
- Add n-user as Approver to the request
- Request available for n-user
- n-user approve request
- remove n-user from the Approver field

Expected result: n-user does not see the request on the Customer Portal
Current Result: n-user continues to see the request.

Now it is clear why your answer does not help in any way?

[John Funk]

Hi Viktar - thank you, that's very helpful and brings clarity to the question. 

Are you clearing the Approval also? Or it was valid for the user to do the Approval and you just don't want them to see it any more? That would be strange if that's the case and Atlassian might not allow that. 

But if that's the case, the only thing I can think of is to implement Issue Level Security and not include the Approvers field for access. When the user needs to approve it, the issue could be assigned to them and the Security Level would include Assignee. Then after the issue is approved and a different person is assigned, the user should lose access. 

If that doesn't work or you don't want to go to that much trouble, you probably need to open a support ticket with Atlassian to get their feedback. And if so, please post their resolution back here. 

[Tony Montana]

@John Funk With the help of Issue Security, this will come out absolutely cumbersome and mediocre. Because there is no way to add system fields, for example, Request Participants. In any other case, approver and people whos creating the request are in same group and in same project role - Service Desk Customer. It means that it is impossible to limit some without limit others.

I think this behavior is a bug.  I will sent this to atlassian