Issue Summary

Dependency not moving to "Committed" while clicking Save once even after Committed by is populated. User needs to click Save twice to move the dependency to Committed which is not expected.

This is reproducible on Data Center: (yes) 

 If "Committed by" is populated with an earlier date than "Needed By" and then changed to same date as "Needed By" then, it takes two clicks on Save button to change/move the dependency from not committed to committed.

What seems to be happenening is, if user has the 'committed By' in the past, the 'proposed' will be set to NO, and once user sets the date to the same as 'needed by', when user clicks Save, this will continue to be set as NO, till user clicks the Save the second time, which causes it to commit.

Note:

• This double Save behavior only happens if the associated Program Increment (PI) has anchor dates that match the dates user is selecting.
• If there are no such anchors, it will auto-commit when user clicks Save the first time as expected.

Steps to Reproduce

1. Create a brand new Program to Program Dependency with default fields such as PI, Feature populated and with some 'Needed By' date (such as 6/27/2024)
2. Prerequisite: Make sure the above PI has anchor dates that match the dates user is selecting in the steps here.
   • For example, for this test, make sure anchor is present that match the date 4/29/2024, such as,( 4/24-4/29)
   • make sure anchor is present that match the date 6/27/2024,  such as,(6/21-6/27)
3. Open the Dependency slide out
4. In the 'Committed By' field, put some earlier date than the above 'Needed By' date (such as 4/29/2024)
5. Save
6. Dependency at this time is 'Not Committed'. Notice the 'Propose Date' is set to 'No'
7. Now change the 'Committed By' to the same date as the 'Needed By' date (such as 6/27/2024). At this stage, both are the same date.
8. Now click Save only once first
9. Notice the dependency is still Not Committed. Notice the 'Propose Date' is still 'No'
10. Now, click Save again.
11. Notice the dependency finally moves to Committed. User needs to click Save twice on the above step for the dependency to move to Committed state which is not expected behavior.

Expected Results

It should require user to click on Save only once to move the dependency to Committed.

Actual Results

User needs to click Save twice to move it to committed.

The behavior changes slightly depending on if you have anchors that match the dates or not, which shouldn't be the case.

Workaround

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