Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

JIRA when sub-issue is created, copy duedate & prioirty field from parent?

Spencer Hoyle
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 28, 2023

I created an automation on when an issue is created. When I am inside an Epic, I clicked the + to create a sub-issue 'Task'. I know it has a parent because I created it from the Epic. However, I get an error.

Any help?

Screenshot 2023-09-28 103920.pngScreenshot 2023-09-28 104036.pngScreenshot 2023-09-28 104118.png

1 answer

0 votes
Laurie Sciutti
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 28, 2023

Hi @Spencer Hoyle and welcome!  If I understand correctly, this is what you want:

Snag_59d36c2.png

Spencer Hoyle
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 23, 2023

Hi Laurie, that is what I want to accomplish! However, when I run the automation i get the output "No Action Performed". It's almost like its a timing issue. It runs the automation before the sub-task has a parent and it says there is no parent. and then it will link it to a parent after the automation

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 23, 2023

Hi @Spencer Hoyle -- Welcome to the Atlassian Community!

Adding to Laurie's answer...

The issue created trigger can fire so quickly that the data is not available for the rest of rule processing...such as using the parent issue's data.

The work-around / fix for that is to always add the Re-fetch Issue action after the Issue Created trigger.  This will slow down the rule by about one second by reloading the data before proceeding.

@Laurie Sciutti -- Spencer noted this was the child issue of an epic, and so the condition you show for a sub-task seems incorrect.  What about this instead:

  • trigger: issue created
  • action: re-fetch issue
  • condition: issue type is Story, Task, or Bug
  • condition: issue has a parent
  • action: edit issue, copying the fields from the parent

Kind regards,
Bill

Like Laurie Sciutti likes this
Laurie Sciutti
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 23, 2023

Thanks, @Bill Sheboy ! 👏🏻

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events