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

Automation for Missing Parent Epic Name

Rachel Stein_h5qqde

Hi! I want to create an automation that fills in the Parent Epic Name field if it is missing, by connecting it to the Epic the issue was created under.

For example, if a feature is created under my "Deals" Epic, but the Parent Epic Name wasn't filled out, the automation would automatically fill the Parent Epic Name field out with "Deals" (i.e. the Epic name)

I've drafted this automation but this is not doing what I want. The JQL is finding features/capabilities with missing Parent Link instead of missing Parent Epic Name field.

Anyone know how to adjust the JQL for this? Thanks in advance!

Accepted answers

Trudy P Claspill

Hello @Rachel Stein

Can you explain the issue type hierarchy for your system?

Are Feature and Capability issue types that you can create as child issues under an Epic directly?

As @Mikael Sandberg showed, if you have the Parent field in your issues then that field will show the key and summary for an issues parent issue You don't need to copy the information to a separate field in the child.

But, if you insist on doing that, and if Feature and Capability are issue types that can be set as children of Epics then I think the query you want is:

issuetype in (Feature, Capability) and Parent is not empty and "Parent Epic Name" is empty

That will get you all Feature and Capability issues that are the child of another issue and that have no value in their "Parent Epic Name" field.

To set that field to the Summary from the issues Parent you would use this smart value as the value for the field:

However, I think your rule still might not work as you expect it to.

Are your running a JQL statement in your Schedule trigger? I ask with a scheduled rule that runs a JQL in the trigger you will execute the "For: JQL" branch for each issue found in the trigger's JQL statement.

All comments

Mikael Sandberg

What you are looking to do in JQL is not possible in the out-of-the-box version. You are looking to do a nested query and that can only be done if you have an app from the Marketplace that extends JQL to allow queries like that.

But why do you need to set the Parent Epic Name field when the parent name will show up in the Parent field?

Screenshot 2024-08-28 at 7.58.21 AM.png

Trudy P Claspill

Hello @Rachel Stein

Can you explain the issue type hierarchy for your system?

Are Feature and Capability issue types that you can create as child issues under an Epic directly?

But, if you insist on doing that, and if Feature and Capability are issue types that can be set as children of Epics then I think the query you want is:

issuetype in (Feature, Capability) and Parent is not empty and "Parent Epic Name" is empty

That will get you all Feature and Capability issues that are the child of another issue and that have no value in their "Parent Epic Name" field.

To set that field to the Summary from the issues Parent you would use this smart value as the value for the field:

However, I think your rule still might not work as you expect it to.

Rachel Stein_h5qqde

Thanks for the reply. The reason I want Parent Epic Name to be filled out with the Epic is because for my Power BI connection, I do aggregations of information at the feature level but show it at the Epic level. Therefore, I need every feature to have the corresponding Parent Epic Name filled out so it flows through correctly to my Power BI.

Rachel Stein_h5qqde

Thanks - appreciate the JQL. This did not work as you expected - it assigned the Parent Epic Name to the Parent, which in this meant all my features got the Capability's name instead of the Epic's name.

I am not running a JQL in the scheduled trigger; I just have it set to run every morning and check through any issues that were added to Jira the day before and make the corrections on issues that satisfy the JQL query.

Any more suggestions for working around this?

Trudy P Claspill

Can you explain the issue type hierarchy for your system?

Are Feature and Capability issue types that you can create as child issues under an Epic directly?

For which issue types are you trying to fill in Parent Epic Name?

Are those issue types direct children of Epics?

Rachel Stein_h5qqde

Hierarchy is as follows: Epic -> Capability -> Feature. I am interested in filling out the Parent Epic Name field of features with the Epic name.

For example, for a feature called "Project XYZ" which is nested under the Epic called "Deals", I want the Parent Epic Name field for that feature to list "Deals".

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