I've created a new issue type in my JIRA staging environment (let's call it BLUE). However, when I fill out and submit BLUE, it gives me an error on required fields that are for a different issue type (let's call it RED).
For example, RED would have "name" as a required field but BLUE wouldn't have the field "name" at all. However, when I submit BLUE it will say "name is required."
Why and how to fix?
If you set up the Field Configuration Scheme of your project so that the Field Config used by the BLUE issue type doesn't have the "name" field as mandatory, I can think of another solution.
Have you looked at the workflow transition? In the Create transition, there might be a validator that checks that "name" has to be filled.
You seem to be talking about 2 different things. The fact that the screens display the fields or not, that's configured in Screen Configuration.
Whether or not the fields are optional or mandatory, displayed or not, is in Field Configurations.
Make sure you're really investigating field configurations and not just screen configurations
Sorry for the confusion. I thought I was investigating screens until I found out "summary" and "description" are mandatory fields in JIRA that are not in field configuration. So, whether or not you display the field or not on your screen is irrelevant it seems; it will give an error because it's a mandatory field in JIRA that's not adjustable in field configurations.
See discussion here: https://answers.atlassian.com/questions/154651
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs