Issue Summary

Capability Target End Date validation fails when parent Epic has no Target Start Date

Steps to Reproduce

1. Create or identify a parent Epic that has a Target End Date populated (e.g., 31/12/2027) but the Target Start Date is left empty.

1. Attempt to create or update a child Capability for this Epic.

1. Set the Capability's Target End Date to a date earlier than the parent Epic's end date (e.g., 30/06/2027).

1. Save the Capability

Expected Results

The system should allow the Capability to have a Target End Date earlier than the parent Epic's Target End Date, as child work is often completed before the overall initiative finishes.

Actual Results

The system throws a validation error. When only the Target End Date is filled on the Epic, Jira Align appears to treat that specific date as both the start and end boundary, effectively forcing all child Capabilities to share the exact same Target End Date.

"Target End Date must be within the date range of the parent Epic."

Workaround

Populate the Target Start Date on the parent Epic. This establishes a valid date range (Start to End) within which child Capabilities can be scheduled.