setSkipScreenCheck is required to update fields on non-default tabs

Summary

 Currently, only fields on Default tab can be updated without using setSkipScreenCheck. setSkipScreenCheck must be used to update fields on non-default tabs.

This contradicts setSkipScreenCheck:

By default, the Issue Service only allows setting values to fields which appear on the screen of the operation which you are performing (e.g. the Edit screen). By enabling this flag, the Issue Service will skip this check.

which means:

• We don't need to use setSkipScreenCheck to set values to fields on screen, no matter which screen tabs they're on.
• We only need to use setSkipScreenCheck to set values to fields that are not on the screen (not on any screen tab).

Steps to reproduce

1. Add fieldA and fieldB to the Default tab of a screen and use that screen in an Issue Operation e.g. Edit Issue
2. Use Java API to edit an issue that uses the screen, updating the values of fieldA and fieldB
3. Edit the screen and add a new tab, then move fieldB to that tab (fieldA remains in Default tab)
4. Repeat step 2

Expected behavior

In both steps 2 and 4 above, both fieldA and fieldB are updated correctly.

Actual Behavior

• At step 2, both fields are updated.
• At step 4, only fieldA which is on the Default tab is updated. fieldB is not updated (because it's on a non-default tab).

Workaround

At step 4, calling issueInputParameters.setSkipScreenCheck(true) before updating fieldB's value.