Scrum to Kanban sending the proposed date on Dependency results in error.

Issue Summary

This is reproducible on Data Center: yes
When I try to add a date in "Committed By" BEFORE the date at "Needed by," I will receive the message:
"The selected Sprint cannot be assigned as the requested end date is before the proposed end date."
If I add the same date in committed by and Needed by, it allows the proposed date to be accepted, and the Dependency gets to the Committed state.
We noticed this is happening when sending a dependency from Scrum to Kanban team; or from Kanban to Scrum team
 

Steps to Reproduce

1. Open a Feature, and create a new Dependency. In "Requesting" field add an Agile team and the "Depends on" with a Kanban team. Choose a date before the Needed By date. Please see the example:
   
2. Click in Accept, and then an error message will appear. The Dependency will not be committed.
   
   "The selected Sprint cannot be assigned as the requested end date is before the proposed end date."
3. Try or create a new dependency, same teams, but in the "Committed By" field, add the same date as "Needed By" you'll be able to accept it, and the Dependency will get to Committed state.
   

Expected Results

When using Kanban teams on Dependencies, we would like to propose a date out of sprint date.

Actual Results

Dates on dates, or sprint date on sprint dates provide a successful outcome but any combination of sprint dates and conventional dates will induce an error where the system does not recognize the dates set

Workaround

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