nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Skip Workflow step based on a value within ticket

Monica_zo7en7

We have a case where depending on a value within our ticket we can skip a step in the workflow. Below is a picture of the field that holds the value "Requestor Employee Type", based on the value of that field is whether or not we would like to skip a step in the workflow. I looked into the automation rules but I can't seem to find a way to have the rule look at that value.

Accepted answers

Kevin Patterson_u4sm4w

Hi @Monica ,

This should be possible in an automation rule. It is difficult to tell in your screenshot but is Request Employee Type HII Mission Tech text inside a table in the description field? If so and assuming it is a text value and not a screenshot of a table you will need to use Regex to extract the value you are looking for and store it in a variable inside your automation rule. here is a link to help with the regex https://confluence.atlassian.com/jirakb/extract-content-out-of-description-and-summary-with-regex-and-automation-1157495262.html

Inside your automation rule you will need to use the Create Variable Action using regex to get your data. I've extracted data from description before using this method but never data inside a table before so i'm not 100% sure if this syntax is correct but it should be close (it is looking for requestor employee type and then returns everything after this value until the next CRLF):

{{issue.description.match("requestor employee type\\s*([^\\r\\n]+)").find(1)}}

Once you have extract the value as a variable, you can use the variable as a condition to check before taking the Transition issue Action to the appropriate status.

All comments

Kevin Patterson_u4sm4w

Hi @Monica ,

{{issue.description.match("requestor employee type\\s*([^\\r\\n]+)").find(1)}}

Once you have extract the value as a variable, you can use the variable as a condition to check before taking the Transition issue Action to the appropriate status.

Monica_zo7en7

Hi @Kevin Patterson it is actually a table, but I will look into this to see if I am able to extract my information and store it in a variable. Thank you!

Kevin Patterson_u4sm4w

Hi @Monica Just out of curiosity where is this data currently collected and how does it make it's way into the description field of a JSM issue? I typically see information like this collected in a JSM request type via a form or custom fields.

Depending on your situation you might be able to improve your requestors experience by collecting this information in a request type that you make available through the helpcenter. Your automation rule would be a bit easier to manage as you wouldn't have to deal with the Regex extraction bit.

Marc -Devoteam-

Hi @Kevin Patterson ,

To be able to achieve this the field value needs to be represented in a custom field.

All information represented in the description field is regarded as text, this doesn't matter if it is in a table or not.

If this values in a custom field you can built an automation rule that based on the field value triggers a transition in the workflow that by passes a certain status.

This transition has to be available or made available in the workflow

Monica_zo7en7

Hi @Kevin Patterson we collect the date thru a confiform on a confluence space we have, then we take all that info using a PowerShell script and create the ticket in Jira.

Kevin Patterson_u4sm4w

@Marc -Devoteam- - it doesnt' necessary have to be in a custom field. We can retrieve the value from the description field using Regex and store it as a variable with the create variable action. I'm just not sure how the markup used to define the table will impact the regex statement.

Monica_zo7en7

@Marc -Devoteam- It seems like the Automation Rule option won't work for what we need. We been considering another option, transition - triggers, have you done anything like what I am trying to do using that option?

Marc -Devoteam-

Hi @Monica

I don't have experience with that.

And if I read up, there is no option to use regex in a transition, on validation or condition

You could look at this issue, as it seems someone has been able to resolve to set variable based on text in a table and use regex for it.

Fetch-information-from-table-in-description-to-custom-fields

I don't like regex options based on text values, as if anything changes the transition based on triggers will be invalid.

The same applies for using it in an automation.

From best practice, I would say store the information within Jira custom fields as that would provide a more stable solution, in my opinion.

You could even look to create a Jira issue direclty from Confiform, instead of a powershell script.

See: Creating+Jira+issue+from+Confluence+with+ConfiForms

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

jira-service-management

jira-service-desk-data-center

jira-service-management-data-center