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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,574
Community Members
 
Community Events
184
Community Groups

Setting custom date field from parent to subtask

Hi,

I am using the behaviour found here: https://scriptrunner.adaptavist.com/5.4.47/jira/recipes/behaviours/subtask-default-fields.html to copy data in system and custom fields from the parent to the sub-task.

I´ve managed to get it to work with all fields except for custom date fields. I´ve written the name of the fields in:

List copyCustomFields =

But it does not work even though it works for all the other fields. I also get an error on the line:

getFieldById(cf.id).setFormValue(outlookDate.formatDMY(parentValue))

Saying: "[Static type checking] - The variable [outlookDate] is undeclared"

What does this mean? Can that have something to do with it?

1 answer

0 votes
John Chin
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.
Jan 27, 2021

Hi @Sebastian Östlund , it seems like you are referring to the old version of the Behaviour article. There is a difference script version in the latest Behaviour Page: 

Please give a try using the latest script from the link above and let us know how it goes.

I did a quick test using the behaviour script on the JIRA date custom field and I can confirm is working. The warning syntax shouldn't be the issue since I got it too. The reason getting the warning is due the method or property is run are looked up when your code is run, not when it’s compiled. I hope this helps.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events