Custom Field Missing From Create Issue Dialog for Some Issue Type

Custom Field(s) that are created after Issue Type being created will not be shown in the Create Issue dialog screen.

Steps to Reproduce

1. Install JIRA and Confluence
2. Create Application Link between JIRA and Confluence
3. In JIRA:
   1. Create new Custom Field and add it to screens. Eg: custom_field1
   2. Mark newly created Custom Field as Required
   3. Create new Issue Type and associate it one of the Project. Eg: Type1
   4. Try to create new issue using the Issue Type "Type1" and the custom_field1 should be be listed as example
      
   5. Create another Issue Type and associated it to the same project . eg: Type3
   6. Create new another Custom Field and add it to the same screen. Eg: custom_field2
   7. Mark the newly created Custom Field as Required
   8. Try to create new issue using the Issue Type "Type1" and the custom_field1 should be be listed as example
      
4. In Confluence:
   1. Create a page
   2. Highlight any of the text and Create Issue
   3. Choose the project and Issue Type "Type3"
   4. Both customfield_1 and customfield_2 will be shown in the dialog as shown in the example below:
      
   5. Highlight another text and Create Issue
   6. Choose the project and Issue Type "Type1"
   7. Create Issue Dialog will shown both customfield_1 and customfield_2

Expected Behaviour

• Both customfield_1 and customfield_2 will be shown in the dialog

Actual Behaviour

• Only customfield_1 will be shown in the dialog while the customfield_2 is not shown
  

Test Environment

This was tested with:

1. Confluence 6.1.3 with JIRA 7.0.10
2. Confluence 6.1.3 with JIRA 7.3.1
3. Confluence 6.6.0 with JIRA 7.5.3

Misc Notes

Problem is NOT fixed after:

• Clearing up plugin cache in Confluence
• Re-indexing from scratch for both JIRA and Confluence
• Restarting JIRA and Confluence
• Re-Creating Application Link
• Marking the custom field as Optional and then Required again
• Switching Issue Type Scheme associated the affected project

Workaround

• Clear the Browser's cache OR
• in Browser's Developer Tool > Applications > Clear Storage