How do I get the "*" to display on required fields when creating a issue/ticket?

[Steve Hooczko]

I want the "*" to show for each required field on the CREATE screen and not allow the user to submit the new ticket until all required fields are filled in.

I configured the fields as required in Field Configuration.

BTW - these fields are custom fields.

[Trudy Claspill · Accepted solution]

Hello @Steve Hooczko 

Can you let us know please if the issue(s) you are creating are in a Team Managed project or a Company Managed project? You can get that information from the Type field on the View All Projects page under the Projects menu.

If the issues are being created in a Company Managed project:

A project uses a Field Configuration Scheme to associate Field Configurations with Issue Types. Confirm that the Field Configuration you updated is included in the Field Configuration Scheme used by the project, and that the same Field Configuration is linked in that scheme to the Issue Type you are creating.

[Steve Hooczko]

Company managed.

[Trudy Claspill]

Have you confirmed that you updated the correct Field Configuration for the issue type you are creating and in the project where you are creating it?

[Steve Hooczko]

yes

[Trudy Claspill]

If you have changed things correctly then the asterisk should appear next to the fields in the Create Issue dialog. And you should not be able to save the issue if the fields are empty.

Can you provide screen images for evidence?

1. An image of the Create Issue dialog showing the project and issue type being created, and one of the fields that you have set to Required but is not showing an asterisk.

2. The Fields page from Project Settings / Issues / Fields showing the Field Configuration Scheme name, and the mapping of Field Configurations to Issue Types.

3. The Field Configuration details (from gear / Issues / Field Configuration) for the Field Configuration that is named in the project's Field Configuration Scheme for the type of issue you are trying to create - including showing the Field from #1 that you have set to Required.

Note that I am just another user of the Jira products. I don't have any access to your system, and I am not a member of Atlassian support. In order to help you debug your situation we need you to provide screen images because we can't look directly at your system.

Thanks!

[Steve Hooczko]

Trudy,

I saved the images to a PPT file on my desktop, but the reply option only accepts a link. How do I get this file to you?

[Trudy Claspill]

Upload images into the post in the community.

[Steve Hooczko]

Logged By

Assigned To

Probable Cause ...

There are several other fields, too, that are setup the same way.

Thanks for helping me with this.

[Steve Hooczko]

[Trudy Claspill]

Thank you for those screen images. That is very helpful.

I can see in the Field Configuration "Field (LifeTrac)" that you have set the Logged By field to Required.

I can see that you have mapped that field configuration to the "Field (LifeTrac)" issue type in the Field Configuration Scheme "Field (LifeTrac)".

And I can see that is the type of issue you are trying to create, and the field is not marked as Required.

The part that is missing is confirming that the Field Configuration Scheme "Field (LifeTrac)" is associated to the project "Field (LifeTrac)".

In the "Field (LifeTrac)" project navigate to Project Settings. Select the Summary option. Check the Fields section to see if it shows that the "Field (LifeTrac)" scheme is associated to the project.

[Steve Hooczko]

Trudy,

That worked!!

That was the one thing I was missing.

Thanks for your help !!!

[Trudy Claspill]

You are welcome!

Since my responses helped you solve your issue, please consider clicking on the Accept Answer button above my initial response.

[Steve Hooczko]

---