Make Assignee field required per project in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Understand how to configure the Assignee field configuration and how you can configure its requirement per project in Jira Data Center.
Solution
Understand the global setting for unassigned issues
The requirement for the Assignee field in Jira is based on the setting Allow unassigned issues found in Jira settings > System > General configuration. It impacts all projects in Jira:
When set to ON, the default value for the assignee field is Unassigned.
When set to OFF, the assignee is required or automatically assigned.
Configure the assignee field per project
Currently, Jira does not support configuring the assignee field behavior per project. The global setting "Allow unassigned issues" affects all projects.
This is a feature request tracked in JRASERVER-1001 - Allow unassigned issues on a per-project basis.
A workaround to enable project-specific behavior is using a third-party app like JSU Automation Suite for Jira Workflows, which has a set of conditions and validations to personalize workflow configuration.
Was this helpful?