Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using smart Value in JQL request in branch

Joss December 22, 2023

Hello ! 

I'd like to do a ticket search with a JQL branch that uses a variable I create and retrieves information with a REGEX match.
But when I run my test with .match I see in the logs that it's empty. Do I have an escapement problem or is it just not possible?

I send screen :

Screen1.pngScreen2.png

 

The result of audit log : 

Error searching for related issues. This is most likely because the following issues don't have a related issue of the type you specified. Try narrowing your search to only include issues that contain links to related issues:

NEX-9: "((Key = ) AND (key != NEX-9)) AND (project in (10014))" - Error in JQL Query: Expecting either a value, list or function but got ')'. You must surround ')' in quotation marks to use it as a value. (line 1, character 9)

 

And finally, the information given in the description of my ticket that should match is: "NEX-1" and I do have an existing ticket named NEX-1.

I've tested this by setting key = NEX-1 directly, and it works fine.

 

So if you can help me, I'd be very grateful!

 

 

 

1 answer

0 votes
Rebekka Heilmann (viadee)
Community Champion
December 22, 2023

What exactly are you trying to achieve?

Where does the second error message come from? I don't see any matching action/condition in your automation branch.

Joss December 22, 2023

What I'm trying to do with the branch is to match a ticket key and then add a comment to this matched ticket.
The initial aim of my approach is to retrieve information from a ticket created by an e-mail request and add a comment to another ticket containing the information from the new ticket created by e-mail.

The second error message come from the branch "For JQL", the error "((Key = ) AND " is empty but I'd like to see the result of my JQL request :

Key = {{issue.description.match("(?i)NEX\s*-\s*[0-9]{1,4}")}}

, which should retrieve the information from the ticket description created following the e-mail request.

I've also tried issuetrigger, but it's no better.

 

Thank you for your reply !

Joss December 22, 2023

I think I've understood where the problem comes from, it's my expression with .match that simply doesn't work since I've tried using {{issue.description}} and I manage to get the desired result.
How would I have to use .match("..regex..") for it to work properly?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events