Why does a custom field that is not configured to any screen show when moving an issue?

[Mike_Low]

After upgrading to Jira Server version 8.3.1 a custom field now displays on the move issue screen (moving an issue between different issue types within the same project). This custom field is not configured to any screen however. Why does it display and how can I prevent it from displaying as it has nothing to do with the project?

I've also gone into create and edit view of an issue with the same issue type being moved to within the project and confirmed that this field is not visible (Using the Configure fields functionality also indicates that the screen is not configured so should not display).

Thanks

[Nic Brough -Adaptavist- · Accepted solution]

Screens are not what determines whether a field is used by a project.  A screen is just a list of fields to show to a user when an action needs to know.

When moving an issue, it's usually important that all possible fields are available to the user.  There is no "move action" that you can tie a screen to, it simply lists all possible fields.

Field context is what determines if a field belongs to a project and issue type.

If you are really desperate to hide a field from move, then you'll need to change the context of the field for both source and target projects, such that the field is not valid for them any more.

[Mike_Low]

Thanks for the response @Nic Brough -Adaptavist-I guess my confusion here is that before the upgrade this field didn't display. What makes it now display. There are plenty of other custom fields that are similarly configured so why don't they display as well. It doesn't seem to make sense that when moving a ticket you are given the option to set a field that will never be visible. I would expect the move screen to apply logic such that:

1. For the issue in its pre-move state: Extract list of all fields with data captured for them

2. For the issue in its post move state (new issuetype and/or project): Extract list of fields configured to any screens for Create, Edit, View operations

3. For any fields that existed pre move that don't exist post move provide option to migrate this data to any available field (from results in step 2)

4. For any fields that didn't exist pre move and that do exist post move give the option to capture new values

To your point changing the context so the custom field is not used by the project in question does hide the field so that solves the problem thank you.