Versions Compared

Key

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

...

  • Priority: id of a valid priority in Jira

  • Summary: String

  • Assignee: accountId of a valid user in Jira

  • Labels: List of strings

  • Description: String

  • Fields of type Paragraph: String

  • Fields of type Text Field: String

  • Fields of type User Picker: accountId of a valid user in Jira

  • Fields of type Multiple User Picker: List of accountIds matching to valid users in Jira

  • Fields of type Date Picker: Date objects

  • Fix Versions: List of fix version ids matching to valid fix versions in the project

  • Fields of type Number: Numeric value

  • Fields of type URL Field: String

...

You can also refer to the values of the other fields in Jira expression. You need to embrace the name of the system field or the id of the custom field with double curly brackets. Note that the value will be available only when the execution of the field behaviour is triggered by the on change event of the field referred.

...

Defining parameters

You can define parameters which will store the data coming from your external APIs. Then, you can use those parameters in the Jira expressions.

...

You can then refer to your parameter in the Jira expression using double curly brackets.

...

Parameters depending on data entered in other fields

You can send the values of fields to your external APIs and set the parameter value according to the response. This also requires that the execution of the field behaviour will be triggered by the change of the field whose value will be sent to the API.

...