This post function enables you to assign an issue to a user using your choice from a variety of user selection strategies categories and user selection categoriesstrategies. It is very simple to configure, and can fit a variety of your needs.
The customization that this post function offers is as follows:
- Only if assignee is empty: First, choose whether this post function executes only when the issue's assignee is set to unassigned.
- User Selection Category: Then, select your user selection category, from which the assignee will be selected. The available categories are:
- Group: Choose one or many group(s)
- Role: Choose one or many project role(s)
- User custom field: Choose one or many user custom field(s)
- Group custom field: Choose one or many group custom field(s)
- User Selection Strategy: Afterwards, choose one of the four user selection strategies, which will be the method in which the issue's assignee is picked.
- Simple round robin: This strategy assigns the users in a circular order, without priority. Every time the post function is executed,
the user next "in turn" is assigned. Once every user in the user selection pool has been assigned to the issue, the strategy circles
back and assigns the issue to first user that was assigned. - Last active user: This strategy assigns the issue to the user who was last active in the issue. It takes into account both the issue's
change history (for example, the user who last caused a transition) and the issue's comment activity. - (*)Total number of assigned issues: With this strategy, the user with the least number of assigned issues in total is selected.
- (*)Total remaining estimation: This strategy selects the user with the least remaining estimate in total across all the issues assigned to them
- Simple round robin: This strategy assigns the users in a circular order, without priority. Every time the post function is executed,
(*) Those user selection strategies also offer the ability to filter the issues onto which those strategies will be applied using a JQL statement. Simply enter your JQL statement and the post function will only consider the issues within the statement's scopeYou can find a description of its capabilities below.
To add the Smart Assignment Post Function:
...
You will be redirected to the following page where you will configure the post function to your liking.
To configure the Smart Assignment post function:
- Enable Only if assignee is empty if if you want this post function to execute only when the issue's assignee is set to unassigned.
- Select your User Selection Category, choose between a Group, Role, User custom field, or Group custom field. Then add one or many item(s) that belong(s) to your chosen category.
- Select your User Selection Strategy, choose between four different selection strategies. Their functionalities are described in the table below
- If applicable, insert your JQL statement to filter the issues that will affect your selected strategy
User Selection Strategy | Description |
---|
(*) Filter |
---|
Issues with JQL | |
---|---|
Simple round robin | This strategy assigns the users in a circular order, without priority. Every time the post function is executed, the user next |
in turn |
is assigned. Once every user in the user selection pool has been assigned to the issue, the strategy circles back and assigns the issue to first user that was assigned. | - | |
Last active user | This strategy assigns the issue to the user who was last active in the issue. It takes into account both the issue's change history (for example, the user who last caused a transition) and the issue's comment activity. | - |
Total number of assigned issues | With this strategy, the user with the least number of assigned issues in total is selected. |
Total remaining estimation | This strategy selects the user with the least remaining estimate in total across all the issues assigned to them. |
(*) |
These user selection strategies also offer the ability to filter the issues onto which those strategies will be applied using a JQL statement. Simply enter your JQL statement and the post function will only consider the issues within the statement's scope. |
That's it, the post function has now been added to the transition!
For the configuration above, you should see the following on the transition page:
Warning | ||
---|---|---|
| ||
|
Info |
---|
Do not forget to publish the workflow! |
...