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

remove "None" form drop down selection?

Chuck Oleary_5s2ckw

I have a screen created that uses a Custom Field that is configured "Select List (single choice)".
I set the Default to one of the choices I created.

Why does the option of "None" still appear as a valid choice when it's not even in the list of choices?

Perhaps I need to make a selection mandatory? I just cannot figure out how to do that.

Accepted answers

All comments

Matt Parks

You do need to make the field required in order for 'None' to no longer show. You will need to do this in the Field Configuration, clicking the 'Required' link for the field in the configuration.

Chuck Oleary_5s2ckw

I don't have that option for my Custom Field. This is on Jira Cloud

Ste Wright

Hi @Chuck Oleary

Field's which are optional need a "None" option - but you can change that (per Project) to make the field mandatory.

Note: This makes it mandatory at creation, and stops a user from clearing values completely.

---

For a Company-managed Project...

Go to Settings (cog icon in top-right) > Issues
Select Field configurations on the left-hand menu
Open the configuration relevant to your Project(s)
Search for this field using the search box, then select the "Required" hyperlink under the Actions column.

A few notes...

You need to make this change per field configuration, across all relevant Projects
If you're unsure which field configuration a Project uses, either...
- Per Project, check via Project Settings > Fields
- Select Field configuration schemes in the admin menu, and review the Projects column. If a Project isn't in there, it's most likely using the "Default" config

---

For a Team-managed Project...

Go to Project Settings > Issue types
Open an issue type
Locate the field, and open its settings (use the ">" icon on the right-hand side)
Check the "Required" checkbox.

A few notes...

You need do this per issue type, per Project for Team-managed

---

Let us know if this helps!

Ste

Matt Parks

This isn't in the Custom Field configuration. There is a Field Configuration section where you would enter this:

I don't know if it looks the same on Cloud, but here is where it is in Data Center:

Chuck Oleary_5s2ckw

Didn't work as expected.

Chuck Oleary_5s2ckw

Turns out that while it removed the None option it caused another problem.

The way I'm using this is when a ticket is in active development and the team needs to pause the work and assign a reason why it's being put on hold. The would select from the dropdown list.

The problem that happened after I made this required is a PM tried to move a ticket from a User Story ticket type to a Bug ticket type. This caused them to get the popup screen, even though it is a new ticket is not being put on hold.

I really do not want to move forward with giving teams the ability to Hold tickets but have the None option as a choice.

I'm baffled on this one, I only want the transition to the Hold status from an active development state to make the Hold reason screen to be presented and the be reason from the dropdown be mandatory.

Matt Parks

Under what conditions should anyone set the Hold Reason field? Should this only happen when transitioning to a particular status?

What problem are you experiencing by allowing None as an option? How are you going to use the information in the Hold Reason field?

The reason I ask these questions is, on the surface, this sounds like a process problem, not a tooling problem. Allow the users to put in a value and, if they don't, have a discussion with them to let them know why it's important to have a value in that field.

You could also set up a query that shows all of the work items in that Hold status that don't have a Hold Reason set. That way you maintain visibility into issues that don't have the value set, so you can reach out to the users that aren't setting the field appropriately to let them know the reason why it's important to set the field.

Chuck Oleary_5s2ckw

What a ticket in a sprint is in an active development state it could be put hold hold for a few reason, like awaiting customer feedback. Since this could take several days or longer we could put the ticket on Hold and I can remove that from the Time In Status reports.
Plus None is not a valid reason so I do not want it selected at all.

We will use the Hold field in PI and sprint metrics. It should give teams an indication where they can improve in splitting tickets, did they miss a DoD, etc.
People over process, why create another dashboard widget that everyone must look at to make sure they didn't take the easy way out and select the nebulous "None" choice.

Regardless if it's a process problem or not, this is what the teams wants to do, why MUST the option of None be there?

Matt Parks

Perhaps I mis-spoke (mis-wrote?) when I said process. I really meant that this is a people issue, not a tooling issue. Let your people know the right thing to do and then trust (but verify) that they're doing the right thing.

The short answer to why 'None' is an option is because, if the field is not required, you have to be able to have no value and, if there was a value selected already, you have to be able to clear it out.

I wasn't recommending that everyone look at the dashboard, just the person(s) who is ultimately responsible for gathering the information around why things are being put on hold.

If you have Scriptrunner, I know it is possible to make a field required only on a particular transition screen through a behavior. You also could make the field required on the workflow transition. In either of these cases, 'None' would not meet the requirement that the field have a value.

IT Group_siq3wx

I have followed the steps for setting the field as required under the field configurations and it still shows none as an option. I even preformed a reindex.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud