Issue Summary

When a user tries to set multiple conflicting contexts for a User Picker field with a filtering option, the same field will display different groups/users based on the type of operation you are performing. (E.g. you will have different options to select when creating an issue, or editing an issue)

Steps to Reproduce

1. Created a custom field called "Test User Picker Context"
2. Created two different contexts for this custom field.
   1. One Global context filtering for "Administrators" group.
      1. This Administrators group contains only three persons (A, B and C)
   2. Another context configured for Test Project specifically.
      1. This other context is filtering for dev-team group (contains 3 other users - D, E, F)
3. Map this "Test User Picker Context" field for all screens in Test Project.
4. When I am trying to create an issue, this "Test User Picker Context" is displaying only users for Administrators group, which is incorrect.
   1. A error message is thrown "User 'xxx' is not valid for this user picker." and it won't let me proceed with the issue creation.
5. When trying to edit an issue, it will display the correct options for the Test User Picker Context custom field.

Expected Results

For all operations (Creating an issue, Editing an issue), all results should match what is configured for the context.

Actual Results

You will see different options to be selected depending on the type of operation you are performing.

Workaround

Change your conflicting custom field's context to not englobe the same Project in multiple contexts.