You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Here is my original requirement:
I want to define due date to each story during the Sprint planning. After that, I would like to sync field value of the story to the "due date" field of all its subtasks.
So that during the daily meeting, we can see the gap between planned due date. (We are using Active Sprint for daily meeting and swiming lane is based on person)
The way I tried to achieve this is:
1. Add due date to both Story and its subtasks
2. Add a transition for Story, the transition will not change status but just trigger a post function to copy the value.
3. Add a "Update Any Issue Field" post function and copy parent field to subtasks.
Now I face an issue for Step 3. Here is my setting for the post function:
Update field on all issues related as | Parent/Sub-Tasks (All Sub-Tasks) |
Perform As User | leave blank |
Issue Field | Due Date |
Field Value | {{issue.parent.fields.duedate}} |
Saved and have a try, then I got a jira ticket update error.
Then I changed the updated field to "Description" just for debug, save and have a try again. I found that the text value "issue.parent.fields.description" is appended to subtasks description. This must be the reason for update failed on due date as it tries to set "issue.parent.fields.duedate" to a date format field that will lead format mismatch.
Actually I got the field value by asking chatgpt, is the usage totally wrong? What could be the best way?