Fred, a regular user, opens a request. Mary, a service desk agent, realizes it needs approval. She clicks 'request for approval', the workflow transition screen pops up, she fills in the details including putting Tom (head of purchasing) as the approver. The field is a user picker that is initially empty (i.e. there is no default value).
An hour later Fred looks at the ticket in the portal and sees that it's in "Needs Approval" state. But he also notices there is an "Approve" button! He mentions this to Mary. Mary looks directly at the ticket in the project and only sees Tom as the approver.
Why does Fred have an 'Approve' button by his name? He should NOT be able to approve his own requests! More important, where is this coming from and how to I disable it?
FYI I checked, there is no post-function that is adding the reporter to the approver custom field...
JIRA Service Desk 3.11.1, Jira 7.81.
it may be that there is a bypass approval transition and this transition is exposed on the portal. Check the workflow and see if there is a bypass transition in addition to the approve transition. if so check if the bypass transition is exposed on portal.
Thanks! I'll check that tomorrow, leaving office now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was it - the transition out of the 'waiting for approval' state was exposed to the portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.