Conditions
The Workflow Constructor supports a wide variety of predefined conditions. These conditions let you describe the basic criteria that must be met to run a workflow rule.
Define the base criteria by dragging conditions to the Prerequisites section of the workflow rule.
When adding multiple conditions, each condition is automatically connected with a logical AND operator. This means that the prerequisite for running the workflow rule is only met when every condition in the Prerequisites section are met.
You can combine conditions in different ways using building blocks. To learn more, see Building Blocks.
Use the Check for additional conditions action to perform additional checks during the transaction. For more information, see Check for Additional Conditions.
This condition checks whether a comment is added to the current issue during the transaction that begins when the workflow is triggered. If a comment is added, the condition is met.
An additional Issue parameter lets you choose which issue the comment must be added to as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the comment must be added to as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether a comment was added to the current issue. | Use a specific issue | Checks whether a comment was added to a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether a comment was added to an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
This condition checks whether a comment is permanently deleted from the current issue during the transaction that begins when the workflow is triggered. If any comment is permanently deleted, the condition is met.
When a comment is deleted but can still be restored, this condition is not met.
An additional Issue parameter lets you choose which issue the comment must be deleted from as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the comment must be deleted from as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether a comment was deleted from the current issue. | Use a specific issue | Checks whether a comment was deleted from a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether a comment was deleted from an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Attachment Is Added
This condition checks whether a file is attached to the current issue during the transaction that begins when the workflow is triggered. If a file is attached, the condition is met.
An additional Issue parameter lets you choose which issue the attachment must be added to as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the attachment must be added to as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether an attachment was added to the current issue. | Use a specific issue | Checks whether an attachment was added to a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether an attachment was added to an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Attachment Is Removed
This condition checks whether an attachment is removed from the current issue during the transaction that begins when the workflow is triggered. If a file is removed, the condition is met.
An additional Issue parameter lets you choose which issue the attachment must be removed from as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the attachment must be removed from as the prerequisite. The following options are available Option | Description |
|---|
Use the current issue | Checks whether an attachment was removed from the current issue. | Use a specific issue | Checks whether an attachment was removed from a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether an attachment was removed from an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. |
|
Issue Link Is Added
This condition checks whether a link to another issue is added to the current issue during the transaction that begins when the workflow is triggered.
An additional Issue parameter lets you choose which issue the link must be added to as the prerequisite. This condition can be further constrained with an optional Link type parameter.
Setting | Description |
|---|
Issue | Determines which issue the link must be added to as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether the link was added to the current issue. | Use a specific issue | Checks whether the link was added to a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether the link was added to an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Link type | Determines which link type must be present to satisfy the condition. When set to Any link type, the condition is met when the issue is linked to any other issue using any link type. To limit the condition to a specific link type, select a link type from the list.
|
Issue Link Is Removed
This condition checks whether a link to another issue is removed from the current issue during the transaction that begins when the workflow is triggered.
An additional Issue parameter lets you choose which issue the link must be removed from as the prerequisite. This condition can be further constrained with an optional Link type parameter.
Setting | Description |
|---|
Issue | Determines which issue the link must be removed from as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether the link was removed from the current issue. | Use a specific issue | Checks whether the link was removed from a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether the link was removed from an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Link type | Determines which link type must be present to satisfy the condition. When set to Any link type, the condition is met when any type of issue link is removed from the issue. To limit the condition to a specific link type, select a link type from the list.
|
Work Item Is Added
This condition checks whether a work item is attached to an issue during the transaction that begins when the workflow is triggered. If a work item is attached, the condition is met.
An additional Issue parameter lets you choose which issue the attachment must be added to as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the work item must be added to as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether a work item was added to the current issue. | Use a specific issue | Checks whether a work item was added to a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether a work item was added to an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Work Item Is Deleted
This condition checks whether a work item is deleted from an issue during the transaction that begins when the workflow is triggered. If a work item is deleted, the condition is met.
An additional Issue parameter lets you choose which issue the work item must be removed from as the prerequisite.
Setting | Description |
|---|
Issue | Determines which issue the work item must be deleted from as the prerequisite. The following options are available: Option | Description |
|---|
Use the current issue | Checks whether a work item was deleted from the current issue. | Use a specific issue | Checks whether a work item was deleted from a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | Checks whether a work item was deleted from an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Has Specific Attributes
This condition checks an issue to see whether one of its attributes meets the specified condition. The condition can be configured to check the current issue or a predefined reference issue.
The condition can be configured to check the issue description, comments, linked issues, or attachments.
For any of these attributes, you have the option to check whether the attribute is empty or not.
For attributes that store a collection (comments, linked issues, or attachments), you can compare the current number of items in the collection to a predefined amount.
Sample scenarios supported by this block include:
Checking the issue for at least one duplicate link.
Performing an action only when the issue description is empty.
Finding issues to update when they contain more than ten comments.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines whether to check the current issue or check the attributes in a specific issue. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks for any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the attributes of a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks for attributes in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Attribute | Determines which issue attribute to check for the specified condition. The following options are available: Option | Description |
|---|
issue description | Checks whether the specified condition applies to the issue description. | comments | Checks whether the specified condition applies to the collection of comments that have been added to the issue. | linked issues | Checks whether the specified condition applies to the collection of links that have been added to the issue. When this option is selected, an additional setting lets you choose which link types should be considered. When set to any link type, the workflow checks for links of any type. To limit the condition to a specific link type, select a link type from the list.
| attachments | Checks whether the specified condition applies to the collection of files that have been attached to the issue. | work items | Checks whether the specified condition applies to the collection of work items that have been added to the issue. |
|
Condition | Determines which condition must apply to the specified attribute in order for the workflow rule to continue processing. The following options are available: Option | Description |
|---|
is not empty | Checks whether the selected attribute stores any data. | is empty | Checks whether the selected attribute doesn't store any data. | is fewer than | Checks whether the number of items stored in the selected attribute is fewer than a specified amount. This option is unavailable for the issue description attribute. | is greater than | Checks whether the number of items stored in the selected attribute is greater than a specified amount. This option is unavailable for the issue description attribute. | is equal to | Checks whether the number of items stored in the selected attribute is equal to a specified amount. This option is unavailable for the issue description attribute. |
|
Amount | Stores the amount used to evaluate the number of items stored in the selected attribute. This option is only visible when the Condition setting is set to is fewer than, is greater than, or is equal to. |
Date Field Matches Specified Criteria
This condition checks the value in a specified date field and determines whether it matches the criteria defined in the block.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines whether to check the current issue or check the field in a specific issue. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the field in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the field in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Field | Specifies which field to check. The available options for this setting are restricted to the set of fields that store dates or dates and times in the projects to which the workflow is attached. |
Happens after | Sets the starting point after which the selected date field is considered. If the value that is stored in the selected field happens before the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The starting point used to determine whether the date field matches the specified criteria can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the starting point. | the value stored in another field | The value that is stored in a second date field is used as the starting point. When used, an additional field for storing the second date field is added to the condition block. | a fixed date | The specified date and time is used as the starting point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Happens before | Sets the end point before which the selected date field is considered. If the value that is stored in the selected field happens after the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The end point used to determine whether the date field matches the specified criteria can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the end point. | the value stored in another field | The value that is stored in a second date field is used as the end point. When used, an additional field for storing the second date field is added to the condition block. | a fixed date | The specified date and time is used as the end point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Issue Is Created Within a Specific Time Frame
This condition checks an issue to see whether it was created within the time frame defined in the block.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the creation date in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the creation date in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Created after | Sets the starting point after which the issue creation will match the condition. If the issue is created before the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The starting point for evaluating the issue creation can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the starting point. | the value stored in another field | The value that is stored in a specific field is used as the starting point. When used, an additional field for storing the date field is added to the condition block. | a fixed date | The specified date and time is used as the starting point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Created before | Sets the end point before which the issue creation will match the condition. If the issue is created after the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The end point for evaluating the issue creation can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the end point. | the value stored in another field | The value that is stored in a separate field is used as the end point. When used, an additional field for storing the date field is added to the condition block. | a fixed date | The specified date and time is used as the end point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Issue Is Updated Within a Specific Time Frame
This condition checks an issue to see whether it was updated within the time frame defined in the block.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the date when the last update was applied to a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the latest update in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. |
|
Updated after | Sets the starting point after which the issue update will match the condition. If the issue update occurs before the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The starting point for evaluating the issue creation can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the starting point. | the value stored in another field | The value that is stored in a specific field is used as the starting point. When used, an additional field for storing the date field is added to the condition block. | a fixed date | The specified date and time is used as the starting point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Updated before | Sets the end point before which the issue update will match the condition. If the issue update occurs after the criteria specified in this setting, the workflow rule will not run. The following options are available: Option | Description |
|---|
any date | The end point for evaluating the issue creation can be any date. | the rule is triggered | The date and time when the workflow rule is triggered is used as the end point. | the value stored in another field | The value that is stored in a separate field is used as the end point. When used, an additional field for storing the date field is added to the condition block. | a fixed date | The specified date and time is used as the end point. When used, an additional field for storing the fixed date is added to the condition block. |
|
Issue Is Created by a Specific User
This condition checks an issue to see whether it was created by a specific user.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks who created a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks who created an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. |
|
Created by | Determines which user needs to have created the issue to satisfy the condition. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the issue was created by the current user. | Use the value from a custom field | The workflow checks the specified field to see if the issue was created by the user who is currently stored as the value for the field. When used, an additional field for storing the user field is added to the condition block. | Use a specific user | The workflow checks to see if the issue was created by the specified user. When used, an additional field for storing the user is added to the condition block. |
|
Issue Is Updated by a Specific User
This condition checks an issue to see whether it was updated by a specific user.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks who updated a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks who updated an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Created by | Determines which user needs to have updated the issue to satisfy the condition. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the issue was updated by the current user. | Use the value from a custom field | The workflow checks the specified field to see if the issue was updated by the user who is currently stored as the value for the field. When used, an additional field for storing the user field is added to the condition block. | Use a specific user | The workflow checks to see if the issue was updated by the specified user. When used, an additional field for storing the user is added to the condition block. |
|
Issue Is Assigned to a Project
This condition checks an issue to see what project it does or does not belong to.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the project in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the project in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Condition | Determines which condition to verify. The following options are available: Option | Description |
|---|
project is | The workflow checks to see if the issue is assigned to the specified project. | project is not | The workflow checks to see if the issue is not assigned to the specified project. |
|
Project | Determines which project is considered to satisfy the specified condition. The following options are available: Option | Description |
|---|
Use a specific project | The workflow checks to see if the condition is true for the issue in the selected project. When used, an additional field for storing the project is added to the condition block. |
|
Field Matches Specified Criteria
This condition check the specified custom field to see whether it matches the criteria defined in the block. The following conditions are supported:
A value for the specified field is set or not.
The field currently stores a specific value or not.
The value for the field changes from one value to another.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the field in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the field in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Field | Determines which field is checked. The selection is limited to the fields that are available in the projects that the workflow is attached to. |
Condition | Determines which condition must apply to the specified field in order for the workflow rule to continue processing. The following options are available: Option | Description |
|---|
is set | Checks whether the selected field stores any value. | is not set | Checks whether the selected field stores an empty value. | is | Checks whether the field is set to a specific value. | is not | Check whether the field is set to any value other than the value that is specified in the condition. | changes | Checks whether the value for the selected field changes from one value to another in the current transaction. |
|
Value | Determines which value must be stored in the selected field to satisfy the condition. This setting is only shown when the Condition is set to is or is not. |
From | to | Determines the starting and ending values that must be present for the selected field to satisfy the condition. These settings are only shown when the Condition is set to changes. |
Issue Attribute Contains a Keyword
This condition checks the current issue to see whether it contains the specified word or words. The condition can be configured to check any combination of issue summary, description, comments, or summaries in linked issues.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the attributes in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the attributes in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Attributes | Determines which attributes to check for the keywords that are specified in the condition block. The following options are available: Option | Description |
|---|
Summary | The workflow checks for the specified keywords in the issue summary. | Description | The workflow checks for the specified keywords in the issue description. | Comments | The workflow checks for the specified keywords in the issue comments. | Summaries in linked issues | The workflow checks for the specified keywords in the summaries of any issues that are linked to the issue. | Work item descriptions | The workflow checks for the specified keywords in descriptions for work items that have been added to the issue. |
You can check for issues that contain keywords in any combination of these attributes. |
Keywords | Stores the keywords that must be contained in at least one of the specified issue attributes for this condition to be met. This setting also supports references to variables that are available in the current context. To browse the list of available fields, click the Insert reference icon. To learn more about references to local variables in workflow rules, see Inserting References to Fields. |
New Issue is Created
This condition checks an issue to see whether it becomes reported in the current transaction. If the issue remains as a draft, this condition is not met.
Issue Becomes Resolved
This condition checks an issue to see whether changes applied to the issue in the current transaction assign it to a state that is considered to be resolved. If the issue remains in an unresolved state, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the state for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the state for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Becomes Unresolved
This condition checks an issue to see whether changes applied to the issue in the current transaction assign it to a state that is considered to be unresolved. If the issue remains in a resolved state, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the state for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the state for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Has Tag
This condition checks whether the specified tag has been added to an issue.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the tags for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the tags for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Tag | Stores the name of the tag that must be added to an issue to satisfy this condition. This setting also supports references to variables that are available in the current context. To browse the list of available fields, click the Insert reference icon. To learn more about references to local variables in workflow rules, see Inserting References to Fields. |
Issue Exists or Is Created
This condition checks whether an issue has already been reported or becomes reported in the current transaction. If the issue remains as a draft, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Is Resolved
This condition checks whether an issue is currently assigned a state that is considered to be resolved. If the issue remains in an unresolved state, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the state for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the state for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Is Starred
This condition checks whether an issue is starred on behalf of the current user
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks for the Star tag in a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks for the Star tag in an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue Is Visible
This condition checks whether a specified user has access to read the issue. If the specified user doesn't have access, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks the access and visibility settings for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks the access and visibility settings for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User | Determines which user the issue should be visible to. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the issue is visible to the current user. | Use the value from a custom field | The workflow checks the specified field to see if the issue is visible to the user who is currently stored as the value for the field. When used, an additional field for storing the user field is added to the condition block. | Use a specific user | The workflow checks to see if the issue is visible to the specified user. When used, an additional field for storing the user is added to the condition block. |
|
Project is Archived
This condition checks whether the specified project has been archived. If the project is active, this condition is not met.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
Project | Determines which project is considered to satisfy the condition. The following options are available: Option | Description |
|---|
Use the project for the current issue. | The workflow checks to see if the current issue belongs to a project that is currently archived. | Use a specific project | The workflow checks to see if the specified project is archived. When used, an additional field for storing the project is added to the condition block. | Take from another block | The rule checks the status of a project that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to a project. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User Can Remove Vote from Issue
This condition checks whether the specified user is allowed to remove their vote from an issue.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
User | Determines which user should be able to remove a vote from the issue. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the current user is able to remove a vote from the issue. | Use the current issue | This setting lets you browse the list of fields that store references to users in the current issue. This can include variables like the owner of the project that the issue belongs to, the user who created or updated the issue, and more. The workflow checks the specified field to see if the user who is currently stored as the value for the field is able to remove a vote from the issue. | Use a specific user | The workflow checks to see if the specified user is able to remove a vote from the issue. When used, an additional field for storing the user is added to the condition block. | Take from another block | The rule checks whether a user who is referenced elsewhere in the workflow rule is able to remove a vote from the issue. This option is only available when the workflow already contains a block that stores a reference to a user. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks whether the user is able to remove a vote from a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks whether the user is able to remove a vote from an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User Can Vote for Issue
This condition checks whether the specified user is allowed to vote for an issue.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
User | Determines which user should be able to vote for the issue. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the current user is able to vote for the issue. | Use the current issue | This setting lets you browse the list of fields that store references to users in the current issue. This can include variables like the owner of the project that the issue belongs to, the user who created or updated the issue, and more. The workflow checks the specified field to see if the user who is currently stored as the value for the field is able to remove a vote from the issue. | Use a specific user | The workflow checks to see if the specified user is able to vote for the issue. When used, an additional field for storing the user is added to the condition block. | Take from another block | The rule checks whether a user who is referenced elsewhere in the workflow rule is able to vote for the issue. This option is only available when the workflow already contains a block that stores a reference to a user. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Issue | Determines which issue to check for the condition. The following options are available: Option | Description |
|---|
Use the current issue | The rule checks any issue that is taken into consideration by the workflow rule. | Use a specific issue | The rule checks whether the user is able to vote for a specific issue. When this option is selected, an additional setting lets you choose which issue should be considered. | Take from another block | The rule checks whether the user is able to vote for an issue that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to an issue. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User Has Role
This condition checks whether the user has been granted the specified role in a specific project.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
User | Determines which user should be assigned the specified role in a project. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the current user is assigned the specified role. | Use the current issue | This setting lets you browse the list of fields that store references to users in the current issue. This can include variables like the owner of the project that the issue belongs to, the user who created or updated the issue, and more. The workflow checks the specified field to see if the user who is currently stored as the value for the field is able to remove a vote from the issue. | Use a specific user | The workflow checks to see if the specified user is assigned the specified role. When used, an additional field for storing the user is added to the condition block. | Take from another block | The rule checks whether a user who is referenced elsewhere in the workflow rule is able to vote for the issue. This option is only available when the workflow already contains a block that stores a reference to a user. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Role | Determines which role must be assigned to the specified user for this condition to be met. The following options are available: Option | Description |
|---|
Use a specific role | The workflow checks to see if the specified user is assigned the specified role. When used, an additional field for storing the role is added to the condition block. | Take from another block | The rule checks whether the user is assigned a role that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to a role. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Project | Determines which project is considered to satisfy the condition. The following options are available: Option | Description |
|---|
Use the project for the current issue. | The workflow checks to see if the user is assigned the specified role in the project that the current issue belongs to. | Use a specific project | The workflow checks to see if the user has the specified role in a specific project. When used, an additional field for storing the project is added to the condition block. | Take from another block | The rule checks whether the user is assigned the specified role in a project that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to a project. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User Is Banned
This condition checks whether the specified user account has been banned and no longer has access to the application.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
User | Determines which user account should be checked. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the current user has been banned. | Use the current issue | This setting lets you browse the list of fields that store references to users in the current issue. This can include variables like the owner of the project that the issue belongs to, the user who created or updated the issue, and more. The workflow checks the specified field to see if the user who is currently stored as the value for the field has been banned. | Use a specific user | The workflow checks to see if the specified user has been banned. When used, an additional field for storing the user is added to the condition block. | Take from another block | The rule checks whether a user who is referenced elsewhere in the workflow rule has been banned. This option is only available when the workflow already contains a block that stores a reference to a user. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
User Is a Member of a Group
This condition checks whether the specified user is a member of a specific group.
Use the following settings to apply additional constraints to this condition block:
Setting | Description |
|---|
User | Determines which user account should be checked. The following options are available: Option | Description |
|---|
Use the current user | The workflow checks to see if the current user is a member of the specified group. | Use the current issue | This setting lets you browse the list of fields that store references to users in the current issue. This can include variables like the owner of the project that the issue belongs to, the user who created or updated the issue, and more. The workflow checks the specified field to see if the user who is currently stored as the value for the field is a member of the specified group. | Use a specific user | The workflow checks to see if the specified user is a member of the specified group. When used, an additional field for storing the user is added to the condition block. | Take from another block | The rule checks whether a user who is referenced elsewhere in the workflow rule is a member of the specified group. This option is only available when the workflow already contains a block that stores a reference to a user. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Group | Stores the name of the group in which the specified user must be a member for this condition to be met. The following options are available: Option | Description |
|---|
Use a specific group | The workflow checks to see if the specified user is a member of the specified group. When used, an additional field for storing the group is added to the condition block. | Use the current issue | This setting lets you browse the list of fields that store references to groups in the current issue. This can include variables like the team for the project that the issue belongs to or issue fields that store references to groups. The workflow checks the specified field to see if the user who is currently stored as the value for the field is a member of the specified group. | Take from another block | The rule checks whether the user is a member of a group that is referenced elsewhere in the workflow rule. This option is only available when the workflow already contains a block that stores a reference to a group. To learn more about references to local objects in workflow rules, see Adding References to Objects. |
|
Last modified: 06 February 2023