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; } } }

Questions on correctly setting variables with regex

Ben Hart_pqfuat

I have the following steps within a single rule:

1. Create variable - {{firstName}}

smart value - {{issue.comments.last.body.match("[A-Za-z]+(?=\.)(?=\.\w+\@jamf\.com)").capitalize()}}

2. Create Variable - {{lastName}}

smart value - {{issue.comments.last.body.match("(?<=\w+\.)[A-Za-z]+(?=\@jamf\.com)").capitalize()}}

3. Create Variable - {{fullName}}

I validated the regex using two different regex sites.. but neither matches on the comment body:

"Alert LMD873080672 status changed: ack ----- Alert lbextd01.fluff.net/LinuxNewProcesses-/opt/cisco/amp/bin/ampdaemon/Status is acknowledged by ben.hart@fluff.com

Previously I had a variable being defined by: {{issue.comments.last.body.match("(\w+\.\w+(?=@))").replace(".", " ")}}. And it worked great! But I need the first and last name variables with proper capitalization in order to use them to assign Incidents. I can't think of a better way other than splitting it, and using .capitalize on each, then recombine them.

Maybe Jira doesn't like Positive lookbehinds?

What am I doing wrong here?

Accepted answers

Bill Sheboy

Hi @Ben Hart

Are you trying to assign the issue using the user name with a Jira Cloud automation rule? If so, that is not possible: the rule will need to use the account ID value for the user.

To get the account ID from the user name, the rule would need to call the REST API user search function using the Send Web Request action.

Kind regards,
Bill

All comments

Ben Hart_pqfuat

I found another, older post where someone was asking something VERY similar. But it worked. Basically I set the initial variable using:

@{{issue.comments.last.body.match("(\w+\.\w+(?=@))").replace(".", " ")}}

Then use a second one with:

Works like a champ! Except now the rule still fails to assign but it's reportedly a permissions issue now. Ill start a new post for that one.

Bill Sheboy

Hi @Ben Hart

Are you trying to assign the issue using the user name with a Jira Cloud automation rule? If so, that is not possible: the rule will need to use the account ID value for the user.

To get the account ID from the user name, the rule would need to call the REST API user search function using the Send Web Request action.

Kind regards,
Bill

Ben Hart_pqfuat

Hey Bill.. So help me understand please. If I add a `Then: Assign the issue to` step. I tried both; assign issue to smart value and specify user. Both of which accept a smart value as a value. So what you are saying is, that won't or is not supposed to work?

Ben Hart_pqfuat

After looking further.. I see the mention that JQL queries can no longer use the dusplay name but user id instead, due to GDPR. But I see nothing in print so far that tells me you cannot assign an issue from a smart value of a users name/dispalyName.

However.. because time is fading and I'm a super anxious person I am now experimenting with a lookup table for name -> id.

Bill Sheboy

Yes, this is a GDPR change impact. For Jira Cloud, I believe the current options are:

long list of if / else conditions, limited to the maximum rule length of 65 components
lookup table, limited to 200 entries for a table
using the Send Web Request action, call the REST API user search to get the user's account ID value
- https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
- https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-rest-api-3-user-search-query-get

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management