Required custom field blocking unrelated issue types

[Marta Caceres]

Hello there, 

I have this project where I have the issue types Epics, Stories, Tasks and Sub-tasks.

Now, there's this custom field (Acceptance Criteria) that I want to be a required field on Epics and Stories, but not on the other issue types.

Initially, I had all the above issue types sharing the screen and screen scheme (Scrum Default Screen Scheme), so the custom field would appear on all issue types.

As I don't want this, I duplicated the screen and screen scheme, removed the Acceptance Criteria field from there, renamed it Scrum Default Screen Scheme - Task / Sub-Task to avoid confusion, and assigned both Task and Sub-task issue types to that scheme. I'd expect for these two issue types to not have the Acceptance Criteria required field present or to block their creation in any way.

However, when creating a Task or Sub-task, indeed the Acceptance Criteria field is not there (not even hidden), but when I try to create the ticket after filling in all the info, it blocks me with a warning saying 'Acceptance Criteria is required' warning.

Upon looking for the Acceptance Criteria field on the Fields Configuration menu, it;s not assigned to any other screen other than the initial Scrum Default Screen, yet it's still affecting the new Scrum Default Screen - Task / Sub-task.

Any ideas on why this is happening? Any thoughts would be greatly appreciated. Thank you!

[Marc - Devoteam · Accepted solution]

Hi @Marta Caceres 

Please check your Field Configuration that issued within the Field Configuration Scheme.

I suspect the field acceptance criteria is set to mandatory.

To achieve what you want, make a copy of the Field Configuration, set the Acceptance Criteria to optional.

Add the Field Configuration to your Field Configuration Scheme, but for all issue types and set the old Field Configuration to the issue types Epic and Story

[Marta Caceres]

Thank you so much for explaining, I was unaware of field configuration and its corresponding schemes. That resolved my issue! 

[Joe Pitt]

As @Marc - Devoteam said, the field configuration needs to be changed 

Yes, as long as it is a different issue type. Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme.  Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html