Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation for Jira: Calculation of date and number fields after fieldChange Edited

Dear forum users,


i need your help with an automation problem: We are using Automation for Jira Server 7.2.3

For recalculation of a derivative due date when another number field is changed we created a Field Value Change Rule with the following edit action:

Field Due date is set to {{issue.customfield_10705.minusWeeks(}}


  • issue.customfield_10705 is a date field and
  • the changed field is a number field

and fieldChange is expected to contain a number, but it seems it doesn't, because everything i tried led to the deletion of the due date. I failed already with:

  • {{issue.customfield_10705.minusWeeks(}}
  • {{issue.customfield_10705.minusWeeks(fieldChange.toString)}}
  • {{issue.customfield_10705.minusWeeks(}}
  • {{issue.customfield_10705.minusWeeks(fieldChange.toString.asNumber)}}
  • {{issue.customfield_10705.minusWeeks(fieldChange.toNumber)}}

Could you please give me a hint how to convert the data in the fieldChange into a number that can be used for calculations ?


Thank you very much for your help in anticipation,


1 answer

Hi @Sebastian L_ 

For something like this, please post an image of your rule to provide some context; that will help the community suggest ideas to you.

Have you tried logging the values to the audit log to see what they contain within the rule?

If your fieldChange field is already a number, you should not need to convert it.  Or, by fieldChange do you actually mean the field which changed to trigger the rule?  If so, please consider directly referencing that field's name (smart value) with no suffix, such as ".to" or ".toString".

Best regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

66 views 2 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you