Understanding the Need for Remapping
If you've renamed the original Jira "Epic" (e.g., to "Feature") for SAFe structuring, manual remapping is necessary. This is due to limitations in reliably identifying the renamed Epic issue-type via the API.
Steps to remap the renamed Epic
Accessing Jira Configuration:
In the piplanning.io RTE Cockpit, navigate to "ALM Configuration" and edit your Jira configuration.
Team Mapping Screen:
Go to the "Team Mapping" screen.
Identifying the Remapping Option:
Scroll down until you see the option for remapping the Epic.
Selecting the Issue-Type:
Choose the issue-type from the dropdown that corresponds to the renamed Jira issue-type.
Changes are applied automatically without the need to click save.
If you did NOT rename you Jira Epic, you will not see this dialog. In that case you do not need to re-map at all.
Additional Note for Multi-Language Setups
If your Jira setup involves multiple languages, you may want to check your Jira fields to ensure proper mapping and synchronization.