I have a ScriptRunner Customer Picker field that presents a list of options retrieved from a REST endpoint. This works just fine and the field is used on a few various screens in different projects.
In one of the projects, the field is on a sub-task screen. I want to use information from the parent issue to filter the list on the sub-task Create Issue screen but I cannot figure out how to access the parent issue information. I can't use the standard "issue" context because it's null since the sub-task has not been created yet.
I can access the parent issue information from a ScriptRunner behavior but I can't figure out how to dynamically alter the picker logic. Even if that's possible ideally I'd like to figure out how to do this in the Script Field so that all the logic is contained in one place.