Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SymbolMeaningPresentationExamples
GEra designatortextAD
CCentury of era (>=0)number20
YYear of era (>=0)year2007
yYearyear2007
xWeekyearyear2007
wWeek of weekyearnumber27
eDay of weeknumber2
EDay of weektextTuesday; Tue
DDay of yearnumber189
MMonth of yearmonthJuly; Jul; 07
dDay of monthnumber10
aHalfday of daytextPM
KHour of halfday (0~11)number0
hClockhour of halfday (1~12)number12
HHour of day (0~23)number0
kClockhour of day (1~24)number24
mMinute of hournumber30
sSecond of minutenumber55
SMilisecondnumber978
zTime zonetextPacific Standard Time; PST
ZTime zone offset/idzone-0800; -08:00; America/Los_Angeles


Base usage example:

On the 2nd screen of the Scheduled Issue wizard, which is named "Set Issue Details" (1), there's a possibility to add above presented predefined variable, into the "Summary" and "Description" fields. In the below picture, I've presented a situation whee "fire count" (2) has been inserted into the "summary" and most of variables possible to enter I've placed in a table - it is possible to use it in "Visual" (6) mode. Left column contains variable meaning (3) and right (4) is a variable itself. In addition to that, the last row, marked in green contains customized own date format. After all was set, I've followed to the next screen by pressing "Next" (7) an saved newly created issue on the third, final screen.

After scheduled issue execution, I've received an expected outcome:


Predefined variables could be used in many ways, here is one of the complex usage examples allowing you to embed images (or link to some external resources), if you know the right pattern: Adding attachments to Scheduled Issues - workaround

...