JIRA-BitBucket integration: custom select fields get reset

Some users like to transition JIRA issues to "Resolved" state using BitBucket integration with JIRA. The JIRA-BitBucket integration seems to have a few issues:

1. The "Visibility" custom field gets reset to the default value "Undecided" when resolving on the BitBucket side. The current value is ignored and overwritten
2. The description of the fields is missing on the BitBucket side
3. The order of the fields is changed on the BitBucket side
4. The "Comment" field is missing on the BitBucket side

The main issue is (1) (the others are cosmetic, (1) corrupts our JIRA issues). Note that "Visibility" is the only custom field with a default and a pre-existing value that we have in that screen, so I can't say the problem is specific to the "Visibility" field or generic to any custom field that might have been pre-existing (as opposed to determined/entered during resolution). In other words, it might be that BitBucket does not (or cannot?) get current values from the JIRA issue. This would explain why it doesn't show the "Verifier" field, but then it should not show the "Visibility" field either.

In the meantime, I need a way to disable JIRA state transitions from within BitBucket, because corrupting the "Visibility" field has customer impact (it changes release noted issues to "internal", even on the external bug management tool side through integration).