wrong field on screen for a particular issue type

[Flavius Nopcea]

What happens when on a screen I put a field that should be given a value for example when an issue is created and that field is not defined for that particular issue type?

Does jira allow this kind of configuration?

[Nic Brough -Adaptavist- · Accepted solution]

If a field has the right context to appear, and is not hidden in the field configurations, then it will appear on your screen. If it is hidden OR does not have the right context (i.e. doesn't belong to the project and/or issue-type) then it will simply not be drawn at all.

[Flavius Nopcea]

but still Jira allows me to put it on the screen right? and the check if it show will be done later, right?

[Nic Brough -Adaptavist-]

Yes, a screen is a list of fields that would appear *if* every field was global. If you hide fields with field configuration or limit them to certain projects/issue-types, then Jira will discard them before showing them to the user.

This lets you do things like "have a single issue creation screen for all projects, but only show the field called root-cause on issue-type called incident"

[Jobin Kuruvilla [Adaptavist]]

Nope. You should associate the field with the issuetype. Otherwise it won't appear on the screen.

[Flavius Nopcea]

but when I create the definition for the screen I can choose from a list of fields. And in that list the field is present. I put the field in the definition of the screen. Is not this an error? Is the check made at the moment the screen is shown?