Bitbucket allows choosing a disabled custom field value on the create Jira issue UI

Issue Summary

When Jira and Bitbucket are integrated through an application link, users can create Jira issues directly from Bitbucket; for example, through a comment on a pull request.

Bitbucket allows users choosing custom field values that were disabled on Jira.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This bug was validated with JSW DC 9.14.0.
2. Create a Software project with sample data.
3. Create a new custom field of type select list (single choice).
   • Add a handful of options.
     
4. Edit options of the default context of this CF and disable one of the options.
   
5. Note that this option won't be available on Jira UI if you try to create an issue.
   
6. Install a vanilla instance of Bitbucket Data Center.
   • This was validated with Bitbucket DC 8.19.0.
7. Create an application link between Bitbucket and Jira.
8. Create a test repository with a couple of files.
9. Make a change and create a Pull Request.
10. Add a comment to the PR.
11. On the comment, click on More actions > Create Jira issue and click on the select list of the custom field.

Expected Results

Bitbucket doesn't show the CF option that was disabled on Jira.

Actual Results

Bitbucket shows the CF option that was disabled on Jira.

Bitbucket runs the following request from the browser:

<BB-Base-URL>/rest/jira-integration/1.0/servers/<applink-ID>/projects/<jira-project-key>/issue-types/<issue-type-ID>/fields-meta

The response has details that a CF option is disabled, but it isn't using that information to hide custom field values.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.