Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,455
Community Members
 
Community Events
185
Community Groups

wrong jql 'epic' regex causing show stopper warning

Edited
issueType = Epic AND status in ('Done') AND issue in linkedIssues({{issue.key}}, 'is implemented by'))

so the above is my jql statement in my jira automation lookup issues action and i'm getting the following warning

 

Invalid JQL

 

Error parsing template: smart values {{parent link}}, {{epic link}} and {{epic}} are deprecated. Please use {{parent}} instead.

 the moment i remove 'issueType = Epic' from my jql, it works fine

fairly certain the regex to flag this error is wrong since i should be able to search for epic issueType, i can't search for parent issue type in this case. the warning is blindly searching for the word epic to flag the error

 

*edit* noticed that jql that doesn't have linkedIssues seems to be fine with epic in it's name

4 answers

1 accepted

0 votes
Answer accepted

This seems to be fixed now and we're free to use "EPIC" without any problems,

Having the same issue:

Can't use {{issue.parent.epic.summary}} anymore

Is this the cause?

https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/

It is related to it but it feel like the validation fails whenever you mention Epic and not only as a smart values. 

0 votes
Adam Rypel _MoroSystems_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 04, 2023

Hi, seems to be some kind of bug - worked for us fine previously and this started happening to us too now. I guess these smart values were removed from Automation and whenever you mention these keywords in jql, it just throws error.

As a temporary workaround, we used IDs of those entities. So for your case, try using ID of Epic issuetype instead of its name. So for example:

issueType = 10000 AND status in ('Done') AND issue in linkedIssues({{issue.key}}, 'is implemented by'))

Having similar issues with automations, seems like whenever I mention Epic it just fails validation 

Daniel Kohn
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 04, 2023

same here, no smart value will work for us when you have "Epic" in the JQL

Suggest an answer

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

Atlassian Community Events