-
Bug
-
Resolution: Fixed
-
Low
-
10.118.2
-
1
-
Severity 3 - Minor
-
No
Issue Summary
The customer removed the committed date from a dependency that already has been set as committed, and changed to Proposed date? field to No and saved. However the dependency is still shown as Committed
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Step 1. Created the dependency - Set Needed by = 12/Apirl/2023 and Set Committed by = 12/Apirl/2023. The dependency is set as Committed
- Step 2. Go To the dependency and remove the committed date and set NO in Proposed date? field
- Step 3. Click Save & Close
- Step 4. Dependency is still set as Committed, Even the committed date is empty
Expected Results
Committed status should be changed when the committed date is removed.
Actual Results
Dependency is still set as Committed, Even if the committed date is empty
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available