Disallowing unassigned issues forces Assignee as Required and breaks Request types

XMLWordPrintable

    • 2
    • Minor

      Issue Summary

      When going to the General Settings page and setting Allow unassigned issues to OFF, Assignee becomes REQUIRED in Field configurations and Request types have it forced on and hidden. Setting the Default Assignee in the Details page of a project to Project lead doesn't automatically address this.

      Steps to Reproduce

      1. Set project to default assign all tickets to Project lead in project Details
      2. Set Allow unassigned issues to OFF in General settings
      3. Receive errors about the Assignee field in all Request types

      Expected Results

      No errors occur and all tickets are automatically assigned to the Project lead.

      Actual Results

      Errors occur due to the Assignee field not having a value.

      Workaround

      Set Allow unassigned issues to ON and use the Default Assignee option the project's Details page or setup an Automation rule to set the Assignee on issue creation.

            Assignee:
            Unassigned
            Reporter:
            Matthew M. (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: