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

We have query related to date assignment to subtasks.

We have tasks and sub-tasks under epic. We also have a custom date field. Whenever this custom field is edited for epic, the same should be copied to its child issues.

 

Kindly suggest a solution for same.

1 answer

1 accepted

0 votes
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 07, 2023

Hi @Kunal Thakale 

You should be able to use Automation for this.

You could use two rules (one for each level) - or you can do it in one rule like this...

  • Trigger: Field Value Changed
    • Field to Monitor = End Date
    • Change Type = Any changes to the field value
    • For = All issue operations
  • Condition: Issue Fields Condition
    • Field = Issue Type
    • Condition = equals
    • Value = Epic
  • Branch: Related Issues
    • Type = JQL
    • JQL - parentEpic = {{triggerissue.key}} and issuetype != Epic
      • Only includes issues that have changed... = FALSE (uncheck)
  • Branch-Action: Edit Issue
    • Field = Date Field
      • Value = Copy Date Field from Trigger Issue

 


A few notes about this rule...

  1. The rule uses a smart value to dynamically find the Children/Sub-tasks in the Branch's JQL
  2. The COPY option in the Action is available via the 3-dots icon next the field's value box - once selected, click on the text to change what issue/field to copy the data from
  3. New changes to the Automation rule execution limits will limit how much use this is for a Free instance - I'd recommend upgrading to Standard or possibly Premium, depending on how many Epics, Children, and Sub-tasks you have

Let us know what you think!

Ste

@Stephen Wright _Elabor8_ 

MicrosoftTeams-image (8).pngMicrosoftTeams-image (7).pngMicrosoftTeams-image (6).png

FYI we have created the automation rule as suggested. The automation works as seen in the audit log, but the custom field is not updated for child issues.

 

I've attached a snapshot referring to it.

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 09, 2023

Hi @Kunal Thakale 

How is the Action setup? A screenshot of that would be useful here.

Ste

Hi @Stephen Wright _Elabor8_ 

 

We didn't get to you. where we can exactly find action setup...?

@Stephen Wright _Elabor8_Please check attachment & let me know if anything required from my end.

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 09, 2023

Hi @Kunal Thakale 

A screenshot of the Action "Edit Issue" (the blue item below your branch) is what I'm referring to here.

Ste

Hi @Stephen Wright _Elabor8_ 

 

Please find the attached screenshot as per your requirement.MicrosoftTeams-image (9).png

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 10, 2023

Hi @Kunal Thakale 

Your edit action is incorrect.  Please refer back to the first post from Stephen when he suggested the value should be copied from the Trigger Issue, not from the Current Issue.

At that point in your rule, Current Issue is the same as the one you are editing and so there will be no changes.

Kind regards,
Bill

Hi @Bill Sheboy 

 

Thanks for your valuable reply.

Like # people like this

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