Hi there,
I am trying to come up with a smooth way to bypass a second approval step based on a value on an issue.
There is a 'Waiting for Approval' status in a workflow. If that is approved if goes to 'L2 Approval Status'
What I would like to happen is if 'L2 Approval' on the issue is FALSE it transitions straight to Waiting for Support.
I have a transition from Waiting For Approval to Waiting for Support called L2 Bypass, just not sure if there is a Post Function I can use and where to put it to check the field on the issue to see if it goes to Approved or to L2 Bypass or I should do this via an automation rule.
The way I have done this, I have a similar use case for application access, is that I have an automation that triggers on the first approval and checks the application selected, and if it does not require second approval the automation will do the approval.
yep done that and works a treat... easy as really when you see how trivial the automation is :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you go into more details about how you completed this? I want to skip a second approval before it hits the second status where the approval is triggered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a link that will explain how to use this "automation" I have a similar issue, I have to skip a workflow step based on the value of a field. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Monica Your rule would basically just have multiple if/else conditions in it. Here is an example from the rule I have for application access:
In this case as you can see if the application = DemoPro or Crayon, the request is moved directly to Approved and will therefor bypass both Manager approval and system owner approval.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg sorry for the question, but in your example, is "application" a field in Jira or a field that is part of the Jira ticket?
I have a field called "company" but when I try to setup the rule I can't make it find that field to compare the value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Monica Application is a field on the request type, it is connected to an Assets object schema that contains all the apps that can be requested through this automated process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg What happens if the field that I need to reference is part of the description of the Jira ticket? how do I reference to it? Here is a screenshot of what I mean. The field I will use to whether or not skip a workflow step is highlighted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can extract it using smart values. For example if your description look something like this:
Application access to: Jira
Then you can extract Jira from that using a smart value like this:
{{issue.description.match("Application access to: (.*)").trim()}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg I don't believe that option given my ticket data, I added a picture to make it more clear what I am working with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ste404 I agree with @Mikael Sandberg You can use an automation to make the approval based on specific criteria. If you do not use automation then you would need an app from marketplace to accomplish this in the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Brant Schroeder Given that I have to use values from within the ticket, do you think the app from marketplace option would be my only option to accomplish this? On a previous reply I show a picture of the value I need to use for my skip.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Monica You can use a smart value to pull information from a table in the description see here: https://community.atlassian.com/t5/Jira-questions/Parse-table-in-Description-column-using-Jira-automation/qaq-p/1474166
If you can it would make it a lot easier to just have a custom field that hold this information and you can reference it in the automation.
After getting all the details I think that JSU or script runner could work but would also have to get the information from the description which will take a little work and understanding of how the app works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Steven,
The 'Fast Track' on a workflow would do this if you have Scriptrunner or an automation rule can also achieve this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.