Not displayed field is marked required

Christof Hurst September 12, 2016

HI,

we have in our project a required field.

This could be filled when editing or closing an issue. On the screen for creating it is not displayed.

But I can't create issues without this field filled.

What can I do? We do not have this information on creating an issue.

Best regards

Christof

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 12, 2016

A field in JIRA is either required or optional when you do it in the field configuration.  You either need to put it on the screen so that it can be filled in (because it's required), or make it optional and do the "mandatory" thing later.

Usually, people use validators in the workflow.  A common example might be a "root cause" field for an incident type issue - you don't know what it is when an incident is raised, so you make it optional in the field configuration.  But on the "close issue" transition, you add a validator to say "you can not close this without something in the root cause field".

Another trick is to use Behaviours from the script runner add-on to make a field effectively mandatory on the front-end with clever rules.  And there are other add-ons which give you some flexibility with mandatory fields in other ways (as well as lots providing clever validators)

Ritu Rao July 24, 2020

I am facing a similar issue. 

The field hasn't even been included for a certain project. But on trying to create an issue it says the field is mandatory.

This particular field is not even visible on issue creation.

Additionally, there are no validators on the workflow of this project.

 

Please help!

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2020

The simplest solution is to make the field optional in the field configuration for the project.

Like Ritu Rao likes this
Ritu Rao July 24, 2020

Thank you!

0 votes
Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 12, 2016

The field has been marked "required" on the field configuration but you need to remove this field from the "Create Issue" screen configuration from the Screen  Scheme Configuration section of the project. Once you remove the field from the screen things should work fine.

Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 12, 2016
Christof Hurst September 12, 2016

The field is not on the create screen.

But as it is marked as required in the field configuration, this seems to be globally for the project and can not be left empty, even is is not on the screen.

Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 12, 2016

May be then you need to have a Field configuration specific to the issueType as it's currently the field configuration is for the whole project.

Anthony E July 13, 2019

Indeed, you need to create a different Field Configuration Scheme for the issue type only and apply to the project.

Suggest an answer

Log in or Sign up to answer