"Jira Issue/Filter" does not update custom field name and removes the custom field from "Columns to display".

Summary

"Jira Issue/Filter" macro does not update custom field name (after changing it in Jira), and removes the custom field from "Columns to display".

Environment

• "Jira" Macro;
• Updating the custom field name, while there is a "Jira Issue/Filter" macro reporting on the old name of the custom field.

Steps to Reproduce

1. Create a page and insert "Jira Issue/Filter" macro into it;
2. Edit the macro > Click the Display options section in this macro > Insert a custom field into "Columns to display" (e.g. 'Test Custom field');
3. Publish the page;
   
4. Navigate to Jira > Edit the name of the custom field (from 'Test Custom field' to something else, like 'Edited Test Custom Field');

Expected Results

• Custom field name to be updated on "Jira Issue/Filter" macro in Confluence;
• Macro to display updated custom field, with its value for each reported issue.

Actual Results

• Custom field name is not updated on "Jira Issue/Filter" macro.
• The old custom field name is still being displayed as a column, but it is empty for every on the list;
  
• Editing the page > Editing "Jira Issue/Filter" macro > Neither Old custom field name ('Test Custom field'), nor the new one ('Edited Test Custom Field') are listed under "Columns to display";
• Note: One additional behavior is that sometimes even though adding the new field's name back to the macro and saving it results in the macro not saving this field, and not displaying it after publishing the page;

Workaround

• Editing the macro > Clicking Display options > Adding the updated custom field name ('Edited Test Custom Field') > Insert
  This workaround forces Confluence to update the macro to include the updated custom field.
• If the macro does not save the updated custom field name, the alternative would be removing the macro alltogether and readding it.