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 to update Parent field when a story is created

Apryl Harris

Hello Community,
I am not new to Jira but do not do very much automation. What I am trying to do shouldn't be that difficult. But my automation is failing and I don't understand why. Please help me.

What I want to do:
Upon creating a "Story" in a specific Jira project, I want to automatically add a specific Parent in the Parent field (using Jira's project automation native feature).

Note: PMOREQ-713 is a valid Epic in this project.

Here's my automation:

The automation audit log (failed) says:

Audit log.JPG

Parent field is not being populated. For the life of me, I cannot figure out why this won't work. Seems simple. Help!

Thank you Community!

Accepted answers

Stephen.Lugton

Hi @Apryl Harris

It looks like you're over complicating it, you don't need the lookup items step, or the advanced editing.

Taking out lookup step, and entering PMOREQ-713 directly in the Parent field should be sufficient to get it working

All comments

Karan Sachdev

Hey @Apryl Harris

Good day!

Could you give it a try by adding a variable after the lookup function that would store the Epic Key? here are some screenshots:

Thanks!

Apryl Harris

HI @Karan Sachdev -

The automation says status = "Success". But the Parent field did not update because the last component of the automation, Edit work item, failed. The error says, "Unable to run this component".

See audit log below:
Audit log #2.JPG

Below is what I have in the Edit work item component:

Automation snippet #3.JPG

I appreciate you helping me resolve this.

Stephen.Lugton

Hi @Apryl Harris

It looks like you're over complicating it, you don't need the lookup items step, or the advanced editing.

Taking out lookup step, and entering PMOREQ-713 directly in the Parent field should be sufficient to get it working

Karan Sachdev

Thanks @Stephen_Lugton

Just validated this, it works by simply typing in the issue key of the Parent.

Thanks!

Apryl Harris

Thanks @Stephen_Lugton

I always try to think KISS (Keep it simple silly). And your simplicity worked!

I was really overcomplicating it!

Again, THANK YOU.

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