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,463,405
Community Members
 
Community Events
176
Community Groups

I am trying to calculate the difference, in days, between the create date and a date custom field.

I am trying to calculate the difference, in days, between the create date and a date custom field.  This usually works but sometimes when there is an update for ScriptRunner the calculation goes off....by very large numbers.  For one issue, I expect a value of 36 and I am getting 3,055,174,244.

Can anyone see anything wrong with my script?  Or what may cause the script to work for a while but then stop?

 

import com.atlassian.jira.component.ComponentAccessor;
import com.atlassian.jira.issue.Issue;
import java.util.Date.*

def customFieldManager = ComponentAccessor.getCustomFieldManager();
def dateFieldObject = customFieldManager.getCustomFieldObject('customfield_10803');
def intTiming=0.0;

def dateFieldObject2 = issue.getCreated();

if(issue.getCustomFieldValue(dateFieldObject) && issue.getCreated()) {
def dateValue = issue.getCustomFieldValue(dateFieldObject) as Date
def dateValue2 = issue.getCreated() as Date
return dateValue - dateValue2

}

1 answer

1 accepted

0 votes
Answer accepted

This is a good question, and I don't know the answer, but my best guess would be that your environment is sometimes returning milliseconds instead of days.

Try an explicit cast to milliseconds and then recalculate the day value, e.g.

def dateValueInMs = dateValue.getTime()

def dateValue2InMs = dateValue2.getTime()

return (dateValueInMs-dateValue2InMs)/1000/60/60/24

Thank you!  I couldn't get the .getTime() to work for me, but I was able to adjust my calculation accounting for the milliseconds.  Just waiting for it to break again.

I appreciate your help!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events