Bypass approval based on Types

[Mario Coluzzi]

Two Request Types share the same Issue Type and the same Workflow.

Workflow:

• Manager Approval --> Rejected
• Manager Approval --> Approved

Logic to apply:

• Request Type 1: it requires manual approval = either rejected or approved
• Request Type 2: it does not require approval = automatically authorized

Automation condition:

• If Request Type EQUALS REQUEST TYPE 2 --> approve automatically

Error:

• No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions.

I have already check if atlassian-addons-project-access has the correct permission and it has and it is in place

Solution:

• I suspect I have to create another Issue Type and apply another Workflow because JSM does not allow such automation

Eager to hear any opinion . . . and no Add-On or Plug-In solution please 

P.S.: this is part of a large automation which I want to keep it small and manageable

[Robert Wen_Cprime_ · Accepted solution]

Hello @Mario Coluzzi 

Are you sure this is for Jira Work Management?  I normally associate Request Types with Jira Service Management.

Is this team-managed or company-managed?  If it were company-managed, I'd set up Workflow Conditions that would show or hide the transitions based on the request type.  This may mean you have to have a transition bypassing the approval.

Can you share a screenshot of your workflow?

[Mario Coluzzi]

Hi @Robert Wen_Cprime_ 

Yes it is Jira Service Management the purpose is to build a quite complex authorization and some requests do not require a Line Manager approval.

Interested in hear more on "show or hide the transitions based on the request type". Can you point me to a documentation? I believe this will address my question.

P.S.: I did attach a screenshot of the issue and the -easy- steps I put in place

[Robert Wen_Cprime_]

Here's the documentation: https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Conditions

This could be a simple Value Field condition that you put on relevant transitions

[Mario Coluzzi]

[facepalm] I cannot believe I missed that easy one. Or maybe I did put in place but left some silly configuration out . . .  times 2 [facepalm]

It works like a charm. Thank you @Robert Wen_Cprime_ 

[Robert Wen_Cprime_]

OK, looking at your automation I wonder if it's executed by the Automation for Jira user.  If it is, is that user one of your defined approvers (I'm guessing you're using the out-of-the-box approval process in JSM)?