User Problem

The customers face challenges in tracking and analyzing Features (Jira Epics) that have been split in Jira Align. Currently, there is no structured way to link or identify split Features or to evaluate the original planned work versus what was completed. While a Parent-Child relationship exists, it does not support split analysis and manual methods like relying on "split" in titles are inconsistent and unreliable. Furthermore, there is no smooth synchronization or reporting for split Features between Jira Align and Jira.

Suggested Solutions

• Linking Split Features
  • Introduce a dedicated field or relationship in Jira Align to link a Feature (Jira Epic) with the Feature from which it was split.
  • Ensure this relationship is searchable and reportable within Jira Align.
• Sync Relationships Between Jira and Jira Align
  • Enable synchronization of related links in Jira to a similar link field in Jira Align, ensuring that split relationships are reflected on both platforms.
• Enhanced Reporting Capabilities
  • Provide consistent reporting capabilities in Jira Align and Jira to analyze split Features and the redistribution of work.
  • Include metrics to evaluate how much of the original planned work was completed before splitting.

Current Workarounds

• Some teams rely on adding "split" to the titles of split Features, but this method is inconsistent and prone to human error.
• Manually tracking relationships and progress across Jira and Jira Align is time-consuming and lacks accuracy.