Issue Summary

When creating an inline issue within a backlog, with a filter on the board which sets a custom field, issue creation can fail, throwing an error about the available options for the field. This looks to be due to the issue being created with an incorrect custom field option, E.G. one that is not available to that projects context. 

Steps to Reproduce

1. Create multiple contexts for a field with the same custom field values 
2. Create a board with a filter to set that field, E.G. 

Project = ABC AND "select list1[Dropdown]" = option123 

1. Create an issue inline via the backlog 
2. If creation succeeds, move the project to the other context, replicating again, it may fail. 

Expected Results

Inline issue creation should be context aware. 

Actual Results

Below excerpt is an example that shows the custom field options that come back, then the allowed custom field options. We see the issue may be attempting to create with the first returned option in the array, "10177" - though this custom field option is confirmed to not be available to this project. 

errors": {
        "customfield_10094": "Specify a valid value for 'select list test'. The allowed values are 10171[option1], 10172[option2], 10173[option3], 10320[option4], -1"
    }, 

"customfield_10094": [
            "10177",
            "10171",
            "10174"
        ]

Workaround

No known work-around - Deleting similar values from other contexts may help, if available.