Issue Summary

Custom issue type mapping is currently allowed to map with the Story type User. Since the Story type User is a default value when syncing the default Jira Story, it causes the "Duplicate story type detected" error, and the Jira issue will not sync.

Steps to Reproduce

1. Have new or existing Custom issue type in Jira
2. Go to Connector > Jira Settings > Custom Issue Types
3. Add new Custom issue type mapping entry and map to Story type User
4. Create a new Jira issue for the above Custom issue type in Jira
5. Wait for the Connector Issue-Sync to trigger

Expected Results

1. Story type User is not available to select from the drop-down menu.

Actual Results

1. Story type User is available to select and if selected, it will cause the "Duplicate story type detected" error.
   
   The below exception is thrown in the xxxxxxx.log file:

    Level: Warning
    MessageTemplate: Duplicate story type detected
   

   Workaround

Do not use the Story type User to map to a Custom issue type ID as it is being used by the default Jira Story sync.