Configure Auto-assignment

You can configure Polarion to automatically assign new or existing Work Items to one or more users based on some condition(s). This is an important feature that can save many hours of work over time. It is recommended that you take the time to become familiar with it, and then set up a default configuration for your system, and specific configurations for projects based on the their individual characteristics.

You can configure one or more Auto-assignment Rules which specify the conditions a Work Item must meet in order for it to be automatically assigned, and the user or users to which it is assigned if the conditions are met. Rules can be defined which apply to all Work Item types, or to one specific type. For example, you might define a rule that says any type of Work Item having a value of usability in the Categories field is automatically assigned to one or more users who are responsible for usability issues.

You can optionally select current user to have new items assigned to the currently logged-in user. By default, current assignee would be applied only if the user is among the possible assignees for the current context. You might want to constrain this further with one or more rule conditions.

Auto-assignment is not active by default. This configuration is available for both global (repository) and Project scope. If you are not familiar with the basics of the different scopes, you may want to review Administration Basics: The Administration Interface.

Access the configuration

  1. Log on with administrator permissions for the scope you want to configure (repository or project).

  2. Enter Administration .

  3. If making a global configuration, select Repository in the Open Project or Project Group dialog box. If making a project configuration, navigate to and select the Project in the Open Project or Project Group dialog box.

    (See Access Projects.)

  4. In the Navigation pane, expand the Work Items node and select Auto-assignment.

    The Auto-assignment page displays a table of the existing auto-assignment rules, if any.

Create a new rule

  • Access the configuration in the desired scope, as described in the previous section.

  • If no rules exist for the current scope, click the Add New Rule button to add an auto-assignment rule. If one or more rules exist, click the Add Rule Below in the row below which the new rule should appear in the table of rules. (Rules are processed in the order listed in the table).

    The Auto-assignment Configuration page appears.

  • In the Conditions section, specify the conditions which must be met in order for Work Items to be automatically assigned. Refer to Quick Help embedded in the page.

  • In the Assignees section, specify one or more users to whom Work Items will be assigned when the conditions specified in Conditions are satisfied.

  • Click the Save button. If you want to create or edit another rule, click the link Return to Auto-assignment.

Modify an existing rule

You can modify existing rules in either the repository or project configuration. A common reason for changing a rule is that the assignee(s) need to be changed due to changes in personnel, responsibilities, etc.

  1. Access the Auto-assignment topic in Administration as described earlier. Be sure you have opened it in the scope you want to configure.

  2. In the table of existing Auto-assignment rules, click the Edit button. The Auto-assignment Configuration page loads.

  3. Edit the Conditions and or Assignees as needed.

  4. Click the Save button. If you want to create or edit another rule, click the link Return to Auto-assignment.

Remove a rule

  1. Access the Auto-assignment topic in Administration as described earlier. Be sure you have opened it in the scope you want to configure.

  2. In the table of existing Auto-assignment rules, click the Remove button and respond to the confirmation prompt.

Warning:

If you have administration permissions for the Repository, be sure you are removing a rule in the correct scope. For example, don't remove a rule in the Repository scope thinking you are doing so for a project.