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

Filling a custom field with an Epic Value Automation Rule

Bernhard BRUNNER_c2lvkd

Hello,

I have a Text custom field for my issues and when there is a subtask created, that it will be filled by a rule with the name of the parentEpic.

Right now the "Then: Edit issue" looks like this:

"customfield_10111": {"value" : "{{parentEpic.name}}"}

how it is described here:

advanced field editing using json

but i get this Error:

"Error while parsing additional fields. Not valid JSON."
I tried it without the "value" and just

"customfield_10111" : "{{parentEpic.name}}"

but same thing.

I also tried just parentEpic, no luck.

In the end I want to have the custom field as a column in my "Issues" query list. So I can see which subtask is in which epic.

Thank you for your help

Accepted answers

Walter Buggenhout

Hi @Bernhard BRUNNER,

For help with automation rules, please share a screenshot of your full automation rule. There's a couple of things we might be able to use, but there's also quite a lot going on in your question that indicates quite a bit of confusion:

instead of {{parentEpic.name}}, I would expect something like {{issue.parent.summary}} if your child issue is a task or story;
and {{issue.parent.epic.summary}} if the issue really is a subtask

Hope this helps!

All comments

Walter Buggenhout

Hi @Bernhard BRUNNER,

instead of {{parentEpic.name}}, I would expect something like {{issue.parent.summary}} if your child issue is a task or story;
and {{issue.parent.epic.summary}} if the issue really is a subtask

Hope this helps!

Shawn Doyle - ReleaseTEAM

Hi @Bernhard BRUNNER

It's not valid JSON as 'parentEpic.name' won't expand.

Use the smart value {{parent.Epic Name}} (include the space between Epic and Name).

Bernhard BRUNNER_c2lvkd

The rule is really basic. When an issue is created and it is a subtask, fill the custom field with the Epic name.
I assumed that parentEpic is the field name of the issue. Because in JQL you can use that to filter through tasks which are inside that Epic name.
I hope that helps with the confusion and will report how it went with your advices. Thanks

Bernhard BRUNNER_c2lvkd

thanks, I assumed that since in JQL you can filter Issues with parentEpic this would be the same name.

I wasnt aware of smart values yet. thanks

Walter Buggenhout

There are still a few potential holes in your use case itself, @Bernhard BRUNNER.

First of all it is not very common to add sub-tasks directly to an epic. They are usually added as child issues to the issue level below epics, most commonly being stories or tasks.

If you add a sub-task to a task, your automation rule is doing nothing to verify if the parent task/story is a child issue of an epic in itself, which may again lead to errors.

Finally, unless your customfield_10109 is a very specific, unsupported field, it would be way easier to select it (by its name) from the dropdown "Choose fields to set" and then add the appropriate smart value there, instead of using the advanced fields syntax. If you decide to do that, make sure to remove the json that is now there, as you can't update the same field twice.

Bernhard BRUNNER_c2lvkd

I am confused, i was trying to find the custom field in the dropdown menu but it didnt show up. I thought because it is a custom field, but now it is there and issue.parent.epic.summary did it.

We have a weird structure in our system, so there is a task between subtask and epic. and all our tasks have epics.
Thanks for your help

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