"Sprints are not mapped in calendar order" warning still displays after 'end-date' based sprint mapping logic is enabled

Issue Summary

Jira Align reports "calendar order" sprint mapping warning which is no longer applicable when end-date based mapping logic is enabled.

"Jira Align team sprints are not mapped in calendar order. Verify that your mappings are correct."

Steps to Reproduce

With new Sprint Mapping logic enabled.

1. Under Admin > Jira Settings > Jira Setup, set 'Sprint mapping logic' = Map sprints based on their end dates and Save.
2. Create out of order closed Jira sprints for an integrated Jira board
   • Unclear how to replicate this, but it is reflected as (closed) Jira Sprints listed out of order in Sprint Report and Jira API sprint output.
3. Sync Board from Admin > Jira Management > Jira Sprints and refresh page

Expected Results

Sprints map correctly without reporting the "calendar order" warning

Actual Results

Sprints map correctly but still report the "calendar order" warning
"Jira Align team sprints are not mapped in calendar order. Verify that your mappings are correct."

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available