You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...so that I can ensure types match across the system as expected and identify what index they are in
π Additional Details
The report should contain, at minimum, the field that is mismatched, the current field type, the expected field type, the JSON schema type, and the index the field belongs to so we can see if this is a problem with a specific LDD, a specific node, or if it is just a one-off issue from older versions of harvest.
Acceptance Criteria
Given When I perform Then I expect
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Node Operator, EN Core Services Operator
πͺ Motivation
...so that I can ensure types match across the system as expected and identify what index they are in
π Additional Details
The report should contain, at minimum, the field that is mismatched, the current field type, the expected field type, the JSON schema type, and the index the field belongs to so we can see if this is a problem with a specific LDD, a specific node, or if it is just a one-off issue from older versions of harvest.
Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered: