Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Learn how to set up, customize, and manage Jira Cloud projects.
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
Learn more on how you can set up Jira Cloud for your team.
Use the 'Fields Required' workflow validator that is packaged in the Jira Suite Utilities.
Please note the following caveats regarding validation of data by the 'Fields Required' workflow validator at the time of issue creation:
fields that you set up as "required fields" are not flagged as such in the form to the end-user
such fields can be cleared at a later time, which is not what you may have intended
plugins will not detect the requirement as implemented by the workflow validator, so may fail later during usage
The reason 3rd party tools are needed is because Jira's interpretation of "required" from a project's field configuration on some custom field means that the field is now required across all screens available to that project, regardless if the screen doesn't actually display that particular field. 3rd party tools, like the Jira Suite Utilities' 'Fields Required' validator, are effectively a more granular means to control fields at the step or screen level at a project, instead of at the project level by the project's field configuration.
Was this helpful?