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; } } }

Assignee field's Required/Optional setting is available in some projects but not in others. How do I make it available in all projects?

Randall Robertson

I am trying to build an issue collector for a specific project but the Assignee field is not visible to anonymous users and is required on this project. Problem: I cannot make Assignee optional because the setting is not available for that field in this project's configuration. "Allow unassigned issues" is ON in general settings. I have some projects where Assignee is optional and at least one where it is not. The setting is available in those other projects. Why would the setting be available in some projects but not in all projects?

The project that does not show the setting was created on an earlier version of JIRA (3.5, probably). The ones that show the optional setting were created either on 4.x or 5.1. Currently running on 5.1.

Accepted answers

Randall Robertson

Confirmed that this simple work-around resolved our problem.

From Atlassian Support:

I have an update from the senior engineer. He wasn't abel to ascertain exactly what was causing the issue but he did discover a workaround. If you set the field to hide and then show this removes the 'required' aspect of the field. This seems to be a bizarre anomaly but this workaround should then allow you to add an issue collector. Let me know if this works or causes any issues. We've tested here and so far that looks viable.

Cheers,
Osman Afridi [Atlassian]
Atlassian Support - San Francisco

All comments

Bhushan Nagaraj2

Hi Randall,

In your project where assignee is required, go to the project's field configuration and check if Assignee is set as a required field.

Read

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour#SpecifyingFieldBehaviour-Makingafieldrequiredoroptional

Cheers

Bhushan

Randall Robertson

I neglected to mention that the Required/Optional setting is unavailable for the Assignee field in the project where Assignee is required. It is available in the other project, though. That is why I am stumped.

Mirek

Hi Randal,

As I know there was no ability to make assignee field required from the field configuration scheme. If you have "Allow Unassigned Issues" set to ON then the only way to make assigne field mandatory is to via third party plugin or some kind of customization (eg. JavaScript modifications)..

Do you have any plugins like JIRA Suite Utilities or using any other that are adding Conditions in the workflow that could make this field mandatory (for example when creating a ticket)? Are you aware about any changes to the JS code or maybe are you using some hidden custom fields that have a harcoded code?

BTW. Could you also check if you have a red star "*" next to the name of the field?

Best Regards,

Mirek

Randall Robertson

Thanks for asking. There is a red star next to the name of the field in the project where Assignee is required. The workflow on that project does not require an assignee be set - we can have an issue set as Unassigned all the way through the process. I don't understand how that can be the case and yet the field is marked as required... I'm trying to set up an issue collector and cannot do so for this project because it complains that the field is required but not visible to anonymous users. For projects where the field is not required, I don't have that problem.

Randall Robertson

Now I have no configurations where Assignee has an Optional/Required setting. Sent Atlassian a service request. We will see what they can tell me.

Nick Jones

Did you manage to solve this? I've exactly the same issue, as I'm trying to use the issue collector. Stumped, and frustrated, too!

Randall Robertson

Working through it with Atlassian support. They don't know what the cause is either. They are going to rebuild my system in a test environment using an anonymized XML dump I am sending them. Only theory at this point is p some problem with system upgrades we have done. If you want to submit a support request, you can mention JSP-170138 for reference.

Randall Robertson

Due to other delays here at work, I only got the xml dump to Atlassian today. So, they are working on checking my system in depth now...

Randall Robertson

Confirmed that this simple work-around resolved our problem.

From Atlassian Support:

I have an update from the senior engineer. He wasn't abel to ascertain exactly what was causing the issue but he did discover a workaround. If you set the field to hide and then show this removes the 'required' aspect of the field. This seems to be a bizarre anomaly but this workaround should then allow you to add an issue collector. Let me know if this works or causes any issues. We've tested here and so far that looks viable.

Cheers,
Osman Afridi [Atlassian]
Atlassian Support - San Francisco