You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

On this page


All date-time values are numeric values representing the number of milliseconds elapsed since January 1, 1970, 00:00:00 GMT.

JWT offers various ways of displaying or calculating with date-time values.

JWT calculated number fields

Dates, times and time zones (function list)

Time Macros

While the number of milliseconds might be useful in some cases, usually you want to retrieve values that are more readable (e.g. when being used in calculated fields).

Macros are aliases for fixed values. They are often used to convert milliseconds to a more accessible value.

Example
timeLogged(subtasks())

This example returns the sum of all time logged on all subtasks of the current issue in milliseconds (see timeLogged() for more examples).

If you want to display the value and maybe compare it wit an original estimate you might need the number of hours instead. Simply divide the results by the {HOUR} time macro and you get the number of hours instead.

timeLogged(subtasks())/{HOUR}


MacroEquivalent value
{SECOND} 1000
{MINUTE} 1000 * 60
{HOUR} 1000 * 60 * 60
{DAY} 1000 * 60 * 60 * 24
{WEEK} 1000 * 60 * 60 * 24 * 7
{MONTH} 1000 * 60 * 60 * 24 * 30
{YEAR} 1000 * 60 * 60 * 24 * 365


The following macros return the day of the week:

Macro Equivalent value
{SUNDAY} 1
{MONDAY} 2
{TUESDAY} 3
{WEDNESDAY} 4
{THURSDAY} 5
{FRIDAY} 6
{SATURDAY} 7

Use these macros in the following functions:

dayOfTheWeek()

dayOfTheWeekToString()

dayOfTheMonth()

dayOfTheYear()



The following macros return the month:

MacroEquivalent value
{JANUARY} 1
{FEBRUARY} 2
{MARCH} 3
{APRIL} 4
{MAY} 5
{JUNE} 6
{JULY} 7
{AUGUST} 8
{SEPTEMBER} 9
{OCTOBER} 10
{NOVEMBER} 11
{DECEMBER} 12

Use these macros in the following functions:

month()

monthToString()


Time zones

Fields of type date and date-time contain a numeric value with the milliseconds elapsed since January 1, 1970, 00:00:00 GMT.

The number that will be returned by any function using a date or date-time timestamp depends on a time zone.

The following time zones are currently available in JWT:

Time zoneOutput
LOCAL or SERVER_LOCALReturns the time zone configured for the server running Jira.
USER_LOCALReturns the time zone of the current user.
RUN_AS_LOCALReturns the time zone of the selected Run as user.

Languages

When dealing with times and time zones sometimes you need to convert them to text. The text returned depends on the selected language.

Currently JWT offers the following language parameters:

Time zoneOutput

SERVER_LANG

Returns the default language configured for the server running Jira.

USER_LANG

Returns the language of the current user.

RUN_AS_LANGReturns the language of the selected Run as user.