Summary

A Jira issue using a custom issue type has been connected to a Jira Align Feature even though the connector settings have been set to map Jira issues of issue type Epic to Jira Align Features

Environment

Jira Align

Diagnosis

• Jira Align > Settings > Jira Settings > Jira Setup > Issue Types > Feature Issue Type ID is confirmed as being set to the correct Epic Issue Type from the Jira instance.
• The View in Jira button in the Jira Align Feature does link to the issue with the custom issue type in Jira.
• The Jira Align Audit log of the Feature  may show an entry by External System containing text similar to
  "Failed to update JiraID : 16130 - Expected AR-218 (16130) to have an issue type id of 10000 and it has an id of 10365 instead. Pushing this update is canceled."
  This message will only be seen if a sync from Jira Align into Jira has been attempted since the mismatch began.

• The Jira History log of the linked issue with the custom issue type shows that a "User updated the Issue Type" changing it from Epic to another type
  

Cause

The Jira issue was initially created as an Epic and this was synchronized as a Feature into Jira Align. Then a Jira user moved the Jira issue, keeping the same Jira project relationship but specifying a different Issue Type during the move operation.

As Jira Align does not support multiple issue types being connected at the feature level, this change of issue type is not shown in Jira Align and sync operations from Jira Align back into Jira will fail. 

Solution

If integration into Jira Align is configured then Jira users should never move any issues that are of Issue type Epic to another Issue Type.

If such an action has been performed then to correct the problem choose one of the following options:

• move the Issue in Jira back to the original issue type - which will maintain the sync of the issue between Jira and Jira Align 
• create a new issue in Jira using the custom issue type and then delete the original issue in Jira and the related Feature in Jira Align - which will result in the issue only being maintained in Jira with no related Feature in Jira Align.