Different screen schemes for different issues type, is it possible?

[Carlo Anapoli]

Hi,

I've set a single Issue type scheme on my Jira. I use only two kind of issues: Task and Meeting.

So, when someone wants to create an issue he can choose from these two possibility.

Clearly I have associate to each type of issue  different screens.

Everything worked properly but now I need to set a "System field" as "Required".

This system field is part of "Task"'s screen but not of the "Meeting"'s screen. So, now, when I create a task it works well but when I try to create a meeting I must to use the "required" field even if it isn't part of the screen.

I think the problem is that I have a single "screen scheme" for the issue operation "create  issue" .

Does someone have some suggestions?

Many thanks

[Joe Pitt · Accepted solution]

Can I have Different Required Fields for Different Issue Types?

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 

[Carlo Anapoli]

Thank you @Joe Pitt