Example: Assign issue to current user if assignee is empty
I would like to automatically assign issue to current user if assignee is empty, but if assignee is not empty, then nothing has to be done.
To implement this behavior we use post-function Set a field as a function of other fields. We have two options, since this post-function have two kind of setting rules: type 1, based in regular expressions, and type 2, which uses boolean expressions. I will explain both solutions:
Using type 1 setting rules, we use post-function Set a field as a function of other fields with the following configuration:
Note that:
- ^$ is regular expression for empty string, and is used to check whether Assignee is empty
%{00020} is code for field Current user
(.*)%{00020}
which is incorrect. Correct setting rule is: (^$)%{00020}
Once configured, transition "Create issue" will look like this:
I have used transition "Create issue" in the example, but you can implement this post-function in any transition of your workflow.
Alternative implementation
Using type 2 setting rules, we use post-function Set a field as a function of other fields with the following configuration
Notice that:
- Value selected in parameter "Field to be checked for matching..." has no effect in this case, since we are only using a type 2 setting rule
%{00003} is code for field Assignee
%{00020} is code for field Current user
Once configured, transition "Create issue" will look like this:
I have used transition "Create issue" in the example, but you can implement this post-function in any transition of your workflow.
Other examples of that function
- Add watcher depending on security level
- Add watchers based on issue type
- Add watchers depending on the value of a custom field
- Assign issue based on the value of a Cascading Select custom field
- Assign issue to a specific user based on a specific custom field value
- Assign issue to current user if assignee is empty
- Assign issue to current user if the user is not member of a certain project role
- Change assignee based on a custom field
- Change parent's status depending on sub-task's summary
- Changing issue priority depending on issue description
- Compose dynamic text by inserting field values in a text template
- Copy "Due date" into a date type custom field in a linked issue if it's greater than current issue's "Due date"
- Limit the number of hours a user can log per day
- Make parent issue progress through its workflow
- Rise priority if due date is less than 3 weeks away
- Set "Due date" depending on the value of other fields, in case it's uninitialized
- Set "Due date" to a specific day of next week no matter of date of creation this week
- Set "Due date" to current date at issue creation if not initialized
- Set a custom field "Urgency" depending on a combined value of issue's priority and "Impact" custom field
- Set a date based on current date
- Set a field based on reporter's email
- Set a watcher at ticket creation depending on custom field's value
- Set assignee depending on issue type
- Set security level based on groups and project roles the reporter or creator are in
- Set security level depending on reporter or creator
- Set the assignee based on a condition
- Set the value of a field of type "User Picker" depending on other field's value
- Set watchers depending on the value of a custom field
- Setting a custom field (User Picker) based on the value of another custom field (Text Field)
- Setting a field's default value depending on another field
- Setting the priority depending on the multiplication of custom fields
- Transition an issue automatically depending on the value of a field
- Unassign an issue when assigned to project leader
- Update checkboxes custom field if a file has been attached during a transition
- Using project properties to calculate custom sequence numbers