Hello,
Today, the Jira-Miro integration is not able to handle this kind of Jira Cascading-Type fields:
When such a field is present for an issue type, the Miro integration does not show the field at all in the integration.
It’s a problem when this field is mandatory in Jira because when creating an issue in Jira via the Miro integration, Jira blocks the creation as it does not have all the required fields. Showing the following error message:
⚠️ Client error (400 BAD_REQUEST) occurred while executing Jira API for instance: {JIRA URL}, TEAM: {ID}. Response body: {"issues":[],"errors":[{"status":400,"elementErrors":{"errorMessages":[]},"errors":{"customfield_28606":"Domains is required."}}],"failedElementNumber":0}]}
If such a field type is present for the main issue types, it completely breaks the integration.
