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

fetch text with automation

FrancoB

Hello everyone,
I have a problem and wanted to ask for advice: I have a field in which a table is contained. Through an automation and a regular expression I fetch words, but I noticed that it also fetches the table and cells in which the words are contained not only. Is there any way to fix this and only fetch the words?
Thanks

Accepted answers

Marc -Devoteam-

Hi @FrancoB

Welcome to the community.

Look at this community request. Tis was recently raised and resolved.

I think it is similar to what you are requesting.

https://community.atlassian.com/t5/Jira-Service-Management/Skip-Workflow-step-based-on-a-value-within-ticket/qaq-p/2751940

All comments

Marc -Devoteam-

Hi @FrancoB

Welcome to the community.

Look at this community request. Tis was recently raised and resolved.

I think it is similar to what you are requesting.

https://community.atlassian.com/t5/Jira-Service-Management/Skip-Workflow-step-based-on-a-value-within-ticket/qaq-p/2751940

FrancoB

Hi @Marc -Devoteam-
thanks for the link it was really helpful to me.
Through this I was able to do partly what I needed to do:
{{issue.description.match(“(?<=\Start:\|)([^|]+)”)}}
I just have a problem that the word I need to search for “Start:” is sometimes written as a hyperlink and therefore is not considered.

Unfortunately I import the text from an email and it contains formatting, I also tried converting it .text but unfortunately I find that the word I need to extract Ex. Home is written under the word Start: and so even then it doesn't work, like this

Start:
Home

Bill Sheboy

Hi @FrancoB -- Welcome to the Atlassian Community!

IMO, the match() function in automation rules does not consistently handle things like text containing newlines, and other formatting. As a result, it can terminate the searching earlier than expected.

A workaround for that is to first replace all the newlines before the match attempt:

{{issue.description.replace("\n", " ").match(your expression)}}

And when the newlines are needed for later processing, they may be first replaced with a known value, and then set back later. For example:

{{issue.description.replace("\n", "~~~").match(your expression).replace("~~~", "\n")}}

Kind regards,
Bill

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-cloud

automation