Summary

When trying to create a new Feature in Jira Align, the error below appears on the audit logs despite all mappings to Jira being set correctly:

Unable to create issue: customfield_25920: Story Type is required.

Solution

According to this article Jira-and-Jira-Align-Integration-Jira-Issue-Field-Best-Practices more specifically to Best Practice #2 section;

Best Practice #2:
Fields that are NOT synced between Jira Align and Jira cannot be marked as required in Jira.

Why:
If an item is created in Jira Align and there is a required field in Jira that does not sync with Jira Align, the sync will fail and the item will not be created in Jira. This is because Jira is looking for the connector to pass this info from Jira Align but it doesn't exist in Jira Align. Since Jira sees this as a required field for creation, it will not create it. This is most common with custom fields.

A minimum list of fields that can be synced from Jira Align to Jira.  There could be more fields listed.

• Epics

  • Name

  • Summary

  • Description

  • Estimate (Points)

  • Acceptance Criteria

  • Assignee

  • Status

  • Fix Version (if used)

  • Labels

  • Issue Type

  • Reporter

  • Program Increment (optional custom field)

  • Parent Jira Epic Name (optional custom field)

  • Why? (optional custom field)

• Stories

  • Summary

  • Description

  • Estimate (Points)

  • Parent Epic

  • Acceptance Criteria

  • Assignee

  • Status

  • Fix Version (if used)

  • Issue Type

  • Labels

  • Epic Link

  • Reporter

  • Sprint

  • Assigned Team (optional custom field)

• Sub-Tasks

  • Summary

  • Description

  • Assignee

  • Parent Story

  • Reporter

• Bug

  • Summary

  • Description

  • Estimate (Points)

  • Assigned Team

  • Sprint

  • Assignee

  • Priority

  • Status

  • State

  • Fix Version

Review the list and confirm any fields that are marked as required are fields that can be synced. Reference list above. If fields are not synced via the connector, they must be changed to Optional.