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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Error with Jira smart values, {{issue.epic.key}} is bugged?


I try to list all stories of an epic using lookup issues, and I use the following query


But it fails... and {{parent}} doesn't work :/

Any idea how I can do that?


3 answers

1 accepted

0 votes
Answer accepted

Oh wow... after so many hours, I found another solution that works.

I use, for the Looup issues, this JQL :

issue in portfolioChildIssuesOf("{{parent}}") AND (type=Story OR type=Defect)

And that's it :) I have my count of stories in {{lookupIssues.size}}

Try replacing the {{issue.epic.key}} with {{issue.parent.key}}

so that it looks like


which should be similar to 


I have used the following, 


to find all sub-task within a task. 

JIra answer.PNG

with the transformation of the hierarchy replacing epic name and epic link to the standard parent, this should work for all issue types in the hierarchy.

"Parent"={{triggerIssue.key}} works, I see the subtasks of the story. But when I try "Parent={{issue.key}} or even "Parent"="DCMB-1482"to be sure I search for an existing epic, it founds 0 results.

Like Patrick Hicks likes this

For automation rules, triggerIssue is to be used.   If you can share information regarding what you are using for the trigger on your rule, this may help define what set issues the lookup component/action is collecting.


This is what I use. Everything that has Epic in it is refused. But the problem is that for my stories, the parent/epic information is stored in parentEpic, not in parent. No idea why.

If I dump {{issue.parent.key}} for my triggered story, it gives me the right value, as well as {{parent}}

issue={{issue}}, parent={{parent}}, pkey={{issue.parent.key}}

issue=DCMB-2491, parent=DCMB-1482, pkey=DCMB-1482


But if I try this in the Issue Navigator, for parent I have no results, and for parent.key :
Field 'parent.key' does not exist or you do not have permission to view it.


How can it even be the same error message? Not existing or not having permission...

I'm wondering what is the relation between the keys used in the query and the Smart values ?

I found some info here :


So that would mean I'm on a Company managed project. Why would there be a difference between the 2 ?

And then Jira is bugged here, as we cannot use "epic" in automation, and it is even not following its documentation. I probably have to open a ticket on their side.

well, it would be


but that return 0 results, when I know that this parent has stories.

I did a lookup just on type='Story', it returns me 100 values, and I dump the parent for each one in logs, they are all empty.

When I use the issue navitagor with a JQL query, I use parentEpic as a key to filter by parent. If I use parent, it is empty.

But I cannot use parentEpic in automation.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events