Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Should we minimize the mandatory fields to allow more flexibility?

A lot of customers like to have a set of mandatory fields here and there for controlling and/or reporting purpose.

I can understand that some fields should in anyway be required for the good processing of the items but where to stop?

Are you in favor to keep required fields as minimal as possible or at the opposite your prefer to have most of the fields under control should this create extra work and reduce flexibility?

Like to read your meaning/advise on this topic


Rilwan Ahmed Community Leader Sep 08, 2022

Hi @Fabrizio Lo Gioco ,

Welcome to the community !!

Some suggestions:

1. Create Field configuration based on different projects or project categories. Mark fields as required there. So any project--> Issue types using this scheme will mark fields as required. 

For Example:
Create ITSM field configuration and map it to ITSM Project
Create Software field configuration and map it to Software category projects 

2. Add Field Required Validator in workflows where you need specific fields to be filled before making any transition. 
Example: Add Field Required Validator For transition from In progress to Resolve. 

Always minimise them, the aim of Jira is to track issues, and that's best done by asking people to fill in everything they can without forcing them to have to think!


Log in or Sign up to comment