Skip to main content
This page was auto-migrated from the legacy ION manual. Some images and cross-links may need follow-up cleanup. Original: _legacy-export/automations/auto-assign-issue-on-creation.md.
Choose who to auto assign an issue to. You can select from the Responsible Engineer or Mechanical Engineer for the part, the creator of the Run the issue was found on, the creator of the Procedure the issue was found on, or a specific Team. You can determine the order by which the assignment will occur. For example, if you configure the assignees as: Responsible Engineer of the part on the Issue, Creator of the Run the Issue was Found On, then Team, this automation will first attempt to assign the issue to the RE. If there is no RE, then it will attempt to assign it to the creator of the run, if there is no run attached, then it will assign it to the specified Team.
These instructions apply to v6 and later of the automation. Older versions will continue to be available. We recommend upgrading your instance to at least v6.

​
How It Works

​
Triggers & Conditions

The automation activates under the following conditions:
  • On Issue Creation:
    • Depending on the configuration of the automation the issue will be assigned to one of the following:
      • Responsible Engineer for the part on the issue
      • Mechanical Engineer for the part on the issue
      • The creator of the run attached to the issue
      • The creator of the procedure attached to the issue
      • The team specified in the configuration

​
Setup

​
Assignee

The Assignee configuration setting allows you to specify the individual that the issue will be assigned to. Additionally, an order is inherently specified with the first value being the first individual to which an assignment is attempted. Click the Add value button to select from the available choices:
  • Responsible Engineer of the Part on the Issue
  • Mechanical Engineer of the Part on the Issue
  • Creator of the Run the Issue was Found On
  • Creator of the Procedure the Issue was Found On
  • Team
You must configure at least one assignee and up to a maximum of 5 (one for each of the above choices). Here is an example configuration: In this example configuration, the automation will first attempt to assign the issue to the Responsible Engineer of the Part on the Issue. If there is no responsible engineer specified on the part, then it will attempt to assign it to the Creator of the Run the Issue was Found On. If the issue is not attached to a run then the automation will attempt to assign the issue to the Mechanical Engineer of the Part on the Issue. The automation attempts to assign the issue based on the order of the assignee setting.

​
Custom Attribute for Responsible Engineer

The custom attribute for responsible engineer is a part level custom attribute. This attribute must exist at the Part level. If you will not be using the Responsible Engineer of the Part on the Issue then this configuration setting can be set as null.

​
Custom Attribute for Mechanical Engineer

The custom attribute for mechanical engineer is a part level custom attribute. This attribute must exist at the Part level. If you will not be using the Mechanical Engineer of the Part on the Issue then this configuration setting can be set as null.

​
Team Name

The name of the team to assign the issue to. If you will not be using the Team assignee then this configuration setting can be set as null.