Investigate substantial_completion_date not matching up with expected date

[mddilley]

Nathan reported a bug around the substantial_completion_date of a project component. The component has a completion_date but no phase so I'm wondering if I need to check back in on the expected behavior of this field. It sounds like there may be a misunderstanding in how this field works.

Currently, this column is calculated by overriding the project substantial completion date with a component's completion date (code) - regardless of whether the component has a phase populated or not.

Nathan said:

Also, I can't figure out why the substantially complete date for
https://mobility.austin.gov/moped/projects/962?tab=map&project_component_id=1266
is 10/1/2023. I'm not going to tamper with this one so you can look into it.

When discussing this further, the behavior of having to clear both the component phase input and the completion date input to re-enable the phase switch caused confusion. We have also flagged this in release testing as well - see row 34 on testing for v2.15.