Upgrade Task is placing Test Environment CF on non Test Exec screens

The Upgrade Task is placing the Test Environment custom field in the Screens that are associated with the View Operation, for Screen Schemes associated with the Default Issue Type on the Issue Type Screen Scheme of each Project.

This is the steps to reproduce the scenario:

1) Picked a Jira instance where Xray was never installed and created some Non Xray projects (In this case the projects where of type Scrum software development): AAP, AAP1, AAP2, AAP3, AAP4 and AAP5

2) For each project I repeated the steps 2.1 and 2.2 below (The below screenshots are from the project AAP, but I repeated the steps for each project):

2.1) Opened its Issue Type Screen Scheme. This is where you can see the association of Screen Schemes and Issue Types:

2.2) In the above view, opened the Screen Scheme associated with the 
Default Issue Type (Used for all unmapped issue types) in this case is the "AAP: Scrum Default Screen Scheme". This redirected me to the Screen Scheme view as shown in the screenshot below - this is where you can see the association between Screens and Issue Operations (View, Edit, Create). Then on this view, made sure I had or else added a Screen to the View Issue Operation:

3) Installed Xray (This was the first time I installed Xray on this instance)

4) Went to check the Screens where Test Environment was installed, this was the result: the Test Environments custom field was added on Screens not used by neither Test Execution or Sub Test Execution issues: