When a Behaviour Initialiser is added to filter the Issue Types, it appears that Advanced Roadmaps' Parent Link field is not able to display the Parent issue if the profile language is changed to any language where the issue type name also changes. 

Steps to Reproduce

1. Ensure that the Advanced Roadmaps plugin is added. Configure the Plan to add a parent issue for the Epic issue type, e.g. Initiative, and create the Initiative.
2. Add a simple Behaviour Initialiser to exclude any issue type as shown below:-

   import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE
   
   getFieldById(ISSUE_TYPE).setFieldOptions(['Epic', 'Initiative', 'Story', 'Task'])
   

3. Change the profile language to either Polish, Portuguese, Romanian or any language where the Epic issue type name is changed to the locale.
4. Create an Epic issue and try to select a parent issue from the Parent Link list.

Expected Behaviour

The Parent Link list must display the Initiative Issue

Actual Behaviour

The Initiative issue goes missing from the Parent Link list as shown in the screenshot below:-

Additional Info

1. The endpoint used to get the parent linked value is http://<JIRA_URL>/rest/jpo/1.0/parent/suggest
2. If you do not set the issue type options field with Behaviour, the issue type names sent to the above URL are in English irrespective of the profile language used as shown in the payload below:-
   
   Below is a screenshot of how the issue type options are displayed in HTML:-
   
3. Else, if the issue type options are changed with Behaviours, the issue type name that is sent to this endpoint is in a Foreign language. Any language where the issue type is spelt differently than English will fail. Below is an example payload when using the Polish language and selecting the Epic issue type as shown in the screenshot below:-
   
   Below is a screenshot of how the issue type options are displayed in HTML:-