Closed ADPennington closed 1 month ago
@robgendron this ticket is a good candidate for the post-parity epic discussed today at x-prod sync.
@robgendron this ticket is a good candidate for the post-parity epic discussed today at x-prod sync.
Added it to the epic, thank you.
@elipe17 and i will schedule a time next week to pair on this ticket.
Aiming to begin on May 30.
Description:
Some STTs have quite a few instances of records where FAMILY_AFFILIATION == 1, RELATIONSHIP_HOH== 1 or 2, and MONTHS_FED_TIME_LIMIT == 0. After discussion with some of these STTs and the DIGIT team, we have decided that the system should allow for this and not raise a category 3 error.
Update: found a similar validator in Section 2 that should also be removed:
validate__FAM_AFF__HOH__Count_Fed_Time
Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
validate__FAM_AFF__HOH__Fed_Time
andvalidate__FAM_AFF__HOH__Count_Fed_Time
in validators.pyvalidate__FAM_AFF__HOH__Fed_Time
andvalidate__FAM_AFF__HOH__Count_Fed_Time
in test_validators.py is up-to-dateNotes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this
/schema_defs/tanf/t2.py
and/schema_defs/tribal_tanf/t2.py
Supporting Documentation: Please include any relevant log snippets/files/screen shots