nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can we make assignee field is mandatory?

Mohamed Ramadan 'JIRA Administrator'

Accepted answers

Nic Brough -Adaptavist-

Nope, I've been really stupid here. I have a blind spot on this particular problem, and I forget it EVERY time it comes up.

I am really sorry.

The advice to turn off "allow unassigned issues" is correct, but you can't make Assignee mandatory with field configurations. Your only option is to put some validators into the workflow. Which is not pretty for the users.

All comments

Nic Brough -Adaptavist-

Field configurations, or turn off "allow unassigned issues" in global configuration.

There is documentation on this stuff you know, and it's searchable - see https://confluence.atlassian.com/display/JIRA/JIRA+Documentation

Mohamed Ramadan 'JIRA Administrator'

Field configuration related to assignee doesn't have required option.

Nic Brough -Adaptavist-

Nope, I've been really stupid here. I have a blind spot on this particular problem, and I forget it EVERY time it comes up.

I am really sorry.

Eli_McGowan

There is some info here:
Making 'Assignee' field required when 'Allow unassigned issues' is turned ON in General Configuration

Basically, it says that you need to use a third-party plug-in: JIRA Suite Utilities

Tom Towkach

It's not perfect, but allow for create issue with unassigned users. Assuming your tickets go to the backlog, it's not a big deal as most backlog items are not being worked on and are generally unassigned.

Then, to transition to via Start Work, or In Progress, place a validator on the Assignee field. The user will get a red error message the Assignee is required.

This makes assignee required to start work on a JIRA configured for unassigned issues.

amit raj_jfashg

you could make assignee field mandatory using scriptrunner, under behaviours

Jeremiah Fischer

I'm faced with this issue and here's what I'm trying out...

Create a single user picker custom field (filtered to the role group I need)
Make the custom field required
Don't display the Assignee role on the create screen
Apply a post-function on the workflow to copy the value from the custom field to the Assignee

I'll update if this works out.

Nope - I ended up going with just a workflow validator on the Assignee. That seems to work perfectly.