Issue Summary

'Set view as default' button in Change Calendar's Admin view settings does not keep JQL intact for the admin user who set up the JQL, when admin navigates away to a different screen and back to change calendar.

Steps to Reproduce

• Use a JSM Space wherein Change Requests are enabled.
• As an admin, navigate to Service Project > Operations > Change calendar.
• In the JQL section, enter your desired JQL and click Search and set it as the default view on Change calendar by clicking the 'Set View as default' in Admin view settings.
• Now navigate to another screen (like Services) and then click on Change Calendar again. The JQL that was set earlier, is not shown.
• As a service desk agent, navigate to the change calendar and confirm that the filtered calendar is shown. So this indicates the JQL filter is saved for other users, but what the admin set as default is not visible to the admin.

Expected Results

• The JQL that the admin setup should stay intact for the admin user.
• Pressing the button should also have some visual feedback. (this is reported in https://jira.atlassian.com/browse/JSDCLOUD-18089)

Actual Results

• The JQL that was setup/the filter that was created by the admin is not shown/persistent for the admin user; However the default view shows up for other users. This creates confusion as the admin is not aware of what they setup as default.
• Clicking the button does not give any visual feedback as well.(this is reported in https://jira.atlassian.com/browse/JSDCLOUD-18089)

Workaround

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