Status
Tech review

Style guide





Short descriptionTimestamp equivalent of any given day plus an offset of n days where weekends don't count.
Output



equivalent of any given day plus an offset of n days where weekends don't count.



Syntax

addDaysSkippingWeekends t, n, time_zone)


If represents a timestamp which coincides with a Friday, adding n = 1 will return a date-time for the following Monday.

Negative values for are used in order to subtract days to t.

(warning) Noten cannot be higher than 50000.

Input

ParameterData typeDescription
t

timestamp returned by a custom field or 
n

Number of days to be added
time_zone

Timezone which will be used to base the calculation on


Output

This expression will return a timestamp as a 

Examples

Parser expressionDescription


timeInStatus("Open", "my_schedule", LOCAL)


Number of milliseconds the current issue has stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.





Syntax


addDaysSkippingWeekends t, n, time_zone)


If represents a timestamp which coincides with a Friday, adding n = 1 will return a date-time for the following Monday.

Negative values for are used in order to subtract days to t.

(warning) Noten cannot be higher than 50000.


Input data type(s)

t:  representing a timestamp
n:  representing the number of days
time_zone: 

Output

Examples



timeInStatus("Open", "my_schedule", LOCAL)

Number of milliseconds the current issue has stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.

timeInStatus("Open", "my_schedule", LOCAL)

Number of milliseconds the current issue has stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.

timeInStatus("Open", "my_schedule", LOCAL)

Number of milliseconds the current issue has stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.