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

Compare with Current View Page History

« Previous Version 26 Next »

Field code
{issue.temporaryNumber1} ... {issue.temporaryNumber5}

Read


Returned valueNumber previously stored in the temporary field
Output data type

NUMBER

Example output10


Write


Valid text input
A text containing base 10 representation of a number
Valid numerical input
Integers, real numbers and also any date-time fields
Example input10

There are 5 temporary number fields.

  • {issue.temporaryNumber1}
  • {issue.temporaryNumber2}
  • {issue.temporaryNumber3}
  • {issue.temporaryNumber4}
  • {issue.temporaryNumber5}

These fields are used to hold temporary numeric and date-time values returned by a post function, which can be used in a subsequent post function within the same workflow transition.

Example

You want to copy the closest due date from all linked issues into a custom field called: Closest due date

Set up a Copy field values from linked issues or subtasks post function to retrieve the closest due date from all linked issues and copy it into the Temporary number 1 field.

Set up a second post function: Copy the temporary value into the custom field.

  • Update fields
  • Closest due date as Target field
  • Value Copy field value from current issue
  • Field Temporary number 1

If you're already familiar with the JWT expression editor, the equivalent behaviour could be implemented by just using Update fields with the following parser expression:

min(fieldValue({issue.dueDate},linkedIssues()))


Conditions using temporary number fields:

  • JQL condition - store the number of issues returned by the JQL in the field temporary number 1.

Please note that:

  • once a transition execution has ended, all temporary fields are cleared.
  • you cannot use temporary fields to pass values from one transition to another.