Verify production info sent to and received from BCA from modernized and legacy systems
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Sharon requested verification of production info sent to and received from BCA from modernized and legacy systems:
"It is important that BC Assessment gets all the updates of changes to ownerships and to locations at all times.
Without these reports working efficiently, will cause both BCA and MHR much grief, as we require tax clearances for many things- which also have to be dealt with at time of sale/transfers."
Attached is a table with some cases to check with BCA some from the modernized system and some from the legacy system.
An API developer need to provide info of one of the latest transactions for these transaction types and we will ask BCA to confirm they received these successfully.
[To check for BCA access to this info.docx](https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBNDRmQlE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--76bf84da140130446f17cbd2cb4c59b0ea245183/To%20check%20for%20BCA%20access%20to%20this%20info.docx)
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the attached “To check for BCA access to this info.docx” table and identify the listed transaction types across modernized and legacy systems. Coordinate with an API developer to obtain one recent transaction for each case, then ask BCA to confirm successful receipt. Done means the listed production updates have been verified or discrepancies are recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100