Issue type screen scheme bug

[Rahul Aich [Nagra]]

Hi All

Today i observed a bug with issue type screen scheme and want to know your opinion before i raise it with atlassian.

I have two issue types - bug and task and have mapped two different screen schemes for the two issue types. (since i want different fields for the two issue types)

Bug issue type has a mandatory field Affect Version(s) however task issue type does NOT have that field on its screen.

Now, the problem is that when i raise a task issue the system asks me that Affect version(s) field is mandatory which i think is wrong since i do not have that field on the task issue screens in the first place(have checked the task create issue screen, also the configure fields on the top right cornor and THE FIELD is not there on both places).

Any ideas?

I m on version 5.0.2 Jira

Rahul

[Nic Brough -Adaptavist- · Accepted solution]

That's not a bug (although it is counter intuitive)

Screens, field configurations, and field contexts are separate things. You have separated the screens out so screen-scheme X is for bugs and screen-scheme Y is for tasks.

But I suspect you have only set up one field configuration, and in there, you've made the field mandatory. It does not matter whether the field is on the screen or not. The scheme doesn't know or care about the screens, all it knows is that you've told it "this field must be filled in". So it demands you fill it in.

Solution - set up a second field configuration, with versions optional (or hidden) and apply that to Task.

[Rahul Aich [Nagra]]

Thanks Nic...yes, i had used the same field configuration which explains the issue.

I did not realise we had the option of configuring field configuration per issue type. I will create 2nd Field config and that should resolve my issue.

Rahul

[Zul NS _Atlassian_]

This is an expected behaviour. You can see the comment by Eric regarding this in here. Alternatively, you can include a workflow condition on the custom field so a warning will show if it is not specified.

[Rahul Aich [Nagra]]

Thanks Zulfadli for your comments. Nic's comment has resolved my issue.

Rahul