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

Need Step by Step Instructions on how to Make a Custom Field Mandatory: Next Gen

Heather Roberts_q9r9jc

I'm trying to add several Custom fields to our tickets that will need to be mandatory and then show up as an option in our tickets. Can someone please give me a step by step guide to adding a custom field to a next gen project that is mandatory? I want it to show up for all tickets types and it's not displaying as an option anywhere.

Thanks

PS I'm aware we are unable to create a mandatory field via settings/issuetypes/ for next gen. My assumption is that it can be done elsewhere and I'm missing it.

Accepted answers

Jack Brickey

Hi Heather, welcome to the Community. For NG projects you cannot make a field required. Note - if it were NG JSD there is an option for what is presented to the customer in the portal. Now to add a field in NG it is pretty straightforward. Just go the Project settings > Issue types and in the right hand sidebar you can create a field.

All comments

Jack Brickey

Heather Roberts_q9r9jc

Good to know it's not just me missing something but I must say, this is pretty disappointing. Why offer your users the ability to do something half way? If we're going to add our own fields, isn't it common sense that we'd want some of them to be required? Thanks for taking the time to answer but this is not the answer I was hoping for.

Jack Brickey

disclaimer: I don't work for Atlassian I'm just a user like yourself. So the following view points are my own.

My view of NG is that it is intended present a more simplified experience that can be used and configured w/o the need of an admin. With that said there is a fine line between simplified and useful in some cases and I concur that being about to specify required fields is important. TBH, I don't use NG much as yet due to the nature of my project needs coupled w/ my comfort zone. All of that said, NG has come a long way and gets better (IMO) daily. There is a NG public roadmap you can watch and you might wish to click on the provide feedback link to let Atlassian know of your interest in having require fields.

Joe Pitt

I agree with @Jack Brickey I used an application years ago where the vendor implemented 'wizards' to make it easier to use. Companies had given them feedback the tool was too complicated and required too much training of administrators. They left everything in place so you could still do everything if you wanted to. NG projects remind me of that. It's too bad most people find out about the shortcoming when they already have projects well underway.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-cloud

required-field