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

Automations - combine smart values

Matt_w0gqa3

Hi, I would like a Jira automation to remove leading and trailing quotation marks from a issue description. Currently I have something that works, but I recognise that it is too resource heavy, how can I combine these steps into one?

1) Trim leading whitespace/newlines: {{issue.description.trim()}}

2) Re-fetch issue data

3) Check if leading quotation mark: {{issue.description.startsWith("\"")}}

4) Remove leading quotaion mark: {{issue.description.substring(1)}}

5) Re-fetch issue data

6) Check if trailing quotation mark: {{issue.description.endsWith("\"")}}

7) Remove trailing quotation mark: {{issue.description.substringBeforeLast("\"")}}

Can this automation be simplified?

Accepted answers

All comments

Bill Sheboy

Hi @Matt

Just to confirm, are you trying to remove only one leading and one trailing quotation mark, if they are present in your description field?

If so, have you tried using the match() function with a regular expression to do that in one step: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match--

Kind regards,
Bill

Matt_w0gqa3

Hi Bill,

Yes that is correct, when copying a cell from Excel it adds quotation marks around the value if the cell contains line breaks. Issue described here.

The output from excel that is pasted into Jira is:

"ABC

123"

There is also a new line added after the trailing quotation mark. I will take a look at the match function, but am not familiar with regular expressions to work this out quickly. Could it also work with the trailing new line? I also want to preserve quotation marks if any exist within the desired description.

thanks

Bill Sheboy

In my experience, the implementation of match() in automation rules has trouble with newlines and regular expressions. And so a work-around for your scenario could be: replace the newlines with a token, perform the match, and swap the token back to newlines.

For example:

{{issue.description.replace("\n","~~").match("^\"?(.*?)\"?$").replace("~~","\n")}}

This one will:

replace any newlines with ~~
perform the match
swap the ~~ back to newlines

Please adjust / test this to meet your needs, and take a look at the documentation to learn about the rule implementation of regular expressions.

I just saw your comment about the extra whitespace, so after you test decide if you want to add a trim() call to help with that.

Matt_w0gqa3

Hi @Bill Sheboy ,

Thanks for your great response, but I have not quite solved my issue.

It seems your solution does not work when there are internal new lines in the description, even if they are replaced with ~~. It seems to break the match and the entire string returned is blank.

I've attached some troubleshooting I did (Note that audit log 6 is your full solution but is cut-off in the view) which I hope enables smarter minds then mine to solve this for me. The first screenshot is when the test description has no internal new lines, and the second screenshot is when there are internal new lines.

no internal new line.png

Edited twice to update the screenshots to make examples clearer

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software