View Issue Permissions for Approvers

[Matthew Berzinskas]

I am trying to find a way to eliminate a redundancy and improve experience for users.

Currently, approvers need to be both in the approver field and a request participant to view the issue they need to approve/reject.

I have seen that I can assign the "Browse issue" permission to the Custom field "Approvers" and then the permission helper says they have access to a test issue.

However, in practice, this doesn't seem to be working.

Is there some other setting that needs to be updated?

Or are there any other best practices here?

Anyone have experience or information on how this should/could work?

[Ste Wright · Accepted solution]

Hi @Matthew Berzinskas 

What's the problem you're trying to resolve here?

Adding the Approver should give them access to the ticket - is this not happening?

Or do you want their access to be revoked post-approval?

Ste

[Matthew Berzinskas]

Hi Stephen, I want approvers to be able to view issues in the portal that they need to review without also having to be a request participant (to save a process step). 

Currently, like Mikael noted, users seemingly can only view issues as participants. 

[Ste Wright]

Hi @Matthew Berzinskas 

Are the Approvers set as Customers in JSM?

I just tested this...

• Added another user to JSM as a Customer (via the user directory)
• Set that user as an Approver on a ticket

...and it let that user see the ticket for approval, without being added separately as a Request Participant.

So it should work just based on the approval being required.

---

Just to be clear...

• The approval process will be set against a field
• The approver needs to be a member of that field
• The approver also needs to be a customer, with relevant project permissions as one
• If there is an issue security scheme in use, you might also need to add approvers here so they can see requests

Ste

[Mikael Sandberg]

Approvers can view the request when it is ready for approval, but if you want the approver to have access to the request before and after the approval is needed then they have to be added as request participants unless you are always sharing requests with the organization. 

[Ste Wright]

That's why I'm asking for clarification, it depends on the need.

Ste

[Matthew Berzinskas]

Hi everyone, thanks for the suggestions. As of now, I am going with the method of approvers having issue access after the approval is ready.

In cases where approvers are known, we are having them added specifically as customers, etc.

[Mikael Sandberg]

The browse project permission would only work if the users have product access to Jira, and they would have to access it from within Jira. For access to the request via the portal the only option is to add them to the request participants field.

So if you need the approvers to have access to the request before and after they have approve the only way to do that is to add them as participants or share the request with the organization.