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 - create story subtasks for specific epic with due date

Tina Leszkiewicz

Hi there.

One of my supervisors requested that I play around and see if I can build one automation that contains both of the following components:

Auto-create subtasks for stories only when the epic = Testing
When/if there is a due date for the story, have the due date for the subtasks be 3 days before the story's due date

I am able to get the automation to create the subtasks for a story, but I can't seem to get it to only create for the specific epic (which has to be assigned after I create the issue).

I'm also having an issue determining the correct format for the due date field. Basically just having issues all around and as a newbie to Jira not quite sure how to build this automation from scratch.

Thanks for any advice

Accepted answers

Jack Brickey

Hi @Tina Leszkiewicz ,

when you say epic = testing, what field are you speaking about, Epic name, custom field other? can you share a screenshot of your current rule? Let me take a stab at creating a rule to share to get you close anyway.

All comments

Jack Brickey

Hi @Tina Leszkiewicz ,

Tina Leszkiewicz

@Jack Brickey

Hi Jack.

I actually was able to figure out how to get the subtask due dates to work! Coding is not even close to my field, but I found a solution online in a different community forum. So the only Issue I'm having is with the epic.

I'm looking for the automation to run only when the epic name is "Testing Epic". The automation seems to run fine with all other aspects, but doesn't seem to work when I add the epic name component.

Here's my current build, including what I have for the epic name, which I though was pretty self-explanatory.

Thanks!

Screen Shot 2022-12-21 at 9.56.13 AM.png

Tina Leszkiewicz

Or perhaps the thing I'm looking for is actually the epic link? Honestly, I'm not too sure what the difference is.

Jack Brickey

Hi @Tina Leszkiewicz ,

Good to hear that you have the date part working. The issue with your epic is that you're using epic name which is only associated with the epic type. What you need is the epic link for the story. The epic link is what points back to the epic parent. What you want to use in pale of your Issue fields condition is a JQL condition - "epic link" = "Testing Epic"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud