What is the most likely cause of the problem?

You have a project with several issue types, associated unique workflows, and a number of components.

The decision has been made to have all new issues assigned automatically.

To that end, you’ve set default assignee(s) for the project lead, component leads, and removed the Assignee field from the screens associated with the Create Issue operation.

One of the issue types is still being created without an Assignee.

What is the most likely cause of the problem?
A . The issue type’s field configuration for Component/s is not set to Required.
B . The default assignee for the issues’ component is still set to Unassigned.
C . The post function Assign to Lead Developer is missing in the create transition.
D . Users creating this issue type do not have the Assign Issue permission.
E . The assignee is being set to Unassigned in the first post-function of the create transition.

View Answer

Answer: E