I have a few different screens created for the same project with different fields being required on different screens. When trying to submit a form for one of the particular screens, I am getting an error message "X Field is Required" even though this field is not on this particular form (it is on another form tied to the same project). Any help to resolve this would be much appreciated. I am using Version 6.0.7
"Field is required" is a flag that has absolutely nothing to do with screens.
You either need to remove the flag in the field configuration, making it optional, or you need to add the field to the screen so the user can obey the mandatory rule you've set.
Thanks for the response. I am getting the field is required error message when I am trying to create an issue. I do not want to make the field optional because it is a field that is on another screen tied to the project (that is required). And I do not want to add this field to this particular screen (where I am getting the field is required error message) because it is not relevant on this screen. Hope this makes sense.
I think you've missed my point.
If a field is mandatory, it is mandatory. So you need to put a value in.
That's it. Screens are irrelevant - you've set up a rule that says "this field must be filled in". So you need to provide a way for the user to fill it in. Which means putting it on the "create" screen. Doesn't matter if you think it's relevant for the screen, you have told Jira that the user must fill it in.
So, again, your choices are
1) make it optional
2) put it on the screen
Note that if you've got a plugin that provides a transition valiator such as "field X is required for this transition", then that you can make the field optional and force entry later in the workflow later. But that's a variation on option 1 above. (I tend to use the one in the "Jira Suite Utilities", but there are others)
IF the screens are tied to different issue types, you can solve this problem by creating a field configuration for each issue type that has different required fields. If it's the same issue type, then Nic is right, you have to either show the field or make it optional.
I am getting the same issue than the one described by TCampbell with JIRA 7.1. I have a simple workflow Create->Review->Resolve->Verify and the Create transition fails due to a field not even used in the "Create" screen but mandatory in the "Review" screen. Until I get a solution/workaround for this, this is simply blocking the implementation of our defect workflow and may postpone JIRA adoption in our company. Is there a known bug/CR in the JIRA issue database?
It is odd. It's happened because of the way Jira evolved early on in its life, and it's something I would dearly love Atlassian to throw away.
The field configuration says "field is mandatory", so you must enter it on the issue. The screen in this case is irrelevant to the logic of the field configuration, Jira just sees the mandatory flag and requires the field to be filled. So, almost incidentally, you have to put the field on the screen, just so a user can meet the requirements of the field configuration.
Ideally, I'd like to see field configurations go away, with most of their functions moving into screens or the custom field definition.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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