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

when creating an issue, getting Please input milestone/label message.

George Grigorian_jtj9vn

Hello,

when creating an issue, I'm getting "Please input milestone/label" message.

This happens even though I have populated the Milestone field. But then I have to also populate the Label field even though the label field is not required.

I should add that this seems to be happening for one type of "issue type", it's called "TestScript" and not like that name makes a difference, but just for point reference. When I tried it with a different "issue type" I didn't have the problem. I will continue to look into that as well, but any thoughts, please?

Required Field issue.png

Accepted answers

Trudy P Claspill

Hello @George Grigorian

Welcome to the Atlassian community.

There are multiple methods to make a field entry required.

The field may be set as Required in a Field Configuration (which can be associated to specific issue types for a given project). In that case you will see the red asterisk next to the field in the Create Issue dialog, and such fields will be required at all times during the issue's lifecycle.

Within the Workflow used by an issue a Validator can be added to an workflow Transition to indicate that a specific field is required when that transition is executed. A "transition" is a change of the issue Status from one value to another. The act of creating an issue is also considered a workflow transition. With a Validator in the transition a field can be made required just at the time of the transition rather than all the time, as is the case with the Field Configuration.

It is likely that the message is being raised by a Validator within the Create Issue transition for the workflow that is used by that specific issue type.

You should alert the Project Administrator for that project and/or the Jira Administrators for your Jira instance, unless you yourself are a Jira Administrator. Administrator access will be required to examine the workflow to determine if that message is indeed being caused by a Validator that is not properly configured.

All comments

George Grigorian_jtj9vn

I should add as well that after I add in a label (even though it's not required), it let's me save it.

Trudy P Claspill

Hello @George Grigorian

Welcome to the Atlassian community.

There are multiple methods to make a field entry required.

It is likely that the message is being raised by a Validator within the Create Issue transition for the workflow that is used by that specific issue type.

George Grigorian_jtj9vn

Thank you Trudy, really appreciate all the details. The field is not set as required. So I am guessing the second suggestion that you kindly have may be what's happening here but I'm still unable to pinpoint it. I may have to reach out to support and create a ticket for it because I don't see any validators added either to the workflow of any of the scenarios. Something's not right somewhere but I still can't find it I will report back here once I figure it out though for sure for everyones benefit. Thank you again.

Trudy P Claspill

Is the project a Team Managed project or a Company Managed project? Team Managed projects don't use Field Configurations and Workflows are managed differently.

Another possibility - do you have the Adaptavist product ScriptRunner Behaviours added to your instance? That is another way that a field can be set as Required, separate from either the Field Configuration or the use of a workflow Validator.

George Grigorian_jtj9vn

you were spot on @Trudy P Claspill of course!! thank you so much! from my support ticket, they gave me a print screen of where these validators are and I was able to find it and remove it. In my almost 10 years of using Jira, I've never heard of Validators before. I learned something new! Thank you as well for giving me the answer. This below print screen is mine and not the one from support.

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