Skip to content
Templating.app Documentation

Define Conditions

Adding Conditions: The Basics

Setting conditions for Description Templates is optional. If you don’t specify any additional conditions besides the project and issue type, the template will apply every time a user creates an issue within the defined project and issue type. However, you can add more conditions to refine when the template should be applied.

Types of Conditions

Field Conditions

Field conditions allow you to define specific requirements based on field values. The following field types are currently supported:

  • Datepicker
  • Datetime
  • Float
  • Multi-checkboxes
  • Multi-select
  • Multi-user picker
  • People
  • User picker
  • Radio buttons
  • Select
  • Textarea (wiki style and basic)
  • Textfield
  • URL
  • Assignee
  • Components
  • Description
  • Fix Version
  • Labels
  • Priority
  • Reporter
  • Summary
  • Issue Type
  • Due Date
  • Target Start
  • Target End
  • Affects Versions

For these field types, you can define the following condition types (vary for each field type):

  • valueIsAfter
  • valueIsBefore
  • valueIsOn
  • valueIsNotOn
  • valueIsEmpty
  • valueIsNotEmpty
  • valueIsGreaterThan
  • valueIsLessThan
  • valueEqualsAnyOf
  • valueNotEqualsAnyOf
  • valuesContainAnyOf
  • valuesContainNoneOf
  • valuesContainAllOf
  • userIsInAnyOfGroups
  • userIsNotInAnyOfGroups
  • valueStartsWithAnyOf
  • valueEndsWithAnyOf
  • valueContainsAnyOf
  • valueDoesNotContainAnyOf

User Conditions

You can also set conditions based on user attributes. These options include:

  • User is in any of the following groups
  • User is not in any of the following groups
  • User has any of the following project roles
  • User has none of the following project roles

To set these, use the group or project role picker within the Behaviour Builder.

Setting Conditions: Step-by-Step

  1. Navigate to the Behaviour Builder in Templating.app. Read our guide for more info.
  2. Select your Description Template or create a new template.
  3. Define additional conditions under the “Conditions” section.
  4. Choose whether all or any of the conditions must be met.
  5. Define your conditions.
  6. Save your updates.

Now your template will only apply when the specified conditions are met, ensuring tailored behavior for your Issue Create Screen.

Adding Multiple Modifications

You can add multiple conditions to a single template, allowing you to handle complex scenarios.

Troubleshooting

  • Warning Sign Next to a Field Type: If you see a warning icon, this means the field is not present on the create screen of the selected issue types. Update your Jira configuration to include the field.
  • Missing Fields: If a field is not listed, it is not yet supported. Field support is determined by Atlassian’s capabilities. Learn more about supported fields on Atlassian’s API reference page.