Expected value for each field type

When setting a field value, the post-function will fail to work as expected, if the input value does not match the expected field type. This document describes the format of values expected by a field when set using a post-function.

The value can be a text provided in the Value field of:

The value can be the result of a Nunjucks template provided in the Value field of:

Text value

The value can be specified as text. It can be:

  • a simple, constant String. For example: This is a description

  • the String representation of a 

    • Number. For example:  3.2

    • Date. The expected format is ISO_8601. For example: 2016-08-05

    • Complex (object) field. In this case, the value should be the String representation of that object. For example, to set the Fix Version/s to version 2.0, you would use the following value: 2.0

Multiple values (for multi-valued fields) can be provided, separated by commas. For example, to specify two Affects Versions 1.0 and 2.0 write 1.0,2.0 in the Value.

For detailed information about the exact format of the expected value for each field, see:

You can also inject Nunjucks annotations into the text valueYou might also want to look at Accessing an issue or a transition using Nunjucks annotations.


JSON value

The value can be specified as a JSON value, which is a text representation of data that can be passed to Jira. This requires the Treat value as JSON option to be selected.

Supported value types include:

  • String. For example: "This is a description"
  • Number. For example: 3.12
  • Date. This must be a String containing an ISO_8601 date. For example: "2016-08-05"
  • Object. The object must contain at least one field (different from id) which allows the object to be identified unambiguously. For example, a user can be specified as:{"accountId":"accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e"}

For multi-valued fields, the value(s) must be provided as an array of values, even if only one value is provided. For example, to set the Fix Versions field to "2.0": [{"name":"2.0"}]

For detailed information about the JSON value expected by each field type, see

You can also inject Nunjucks annotations into the JSON valueYou might also want to look at Accessing an issue or a transition using Nunjucks annotations.