Support of Continuation In filing for Go-Live in Prod
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
@mstanton1 @severinbeauvais
Based on IT OPs ticket https://sbc-registries.atlassian.net/jira/servicedesk/projects/ITOPS/queues/custom/36/ITOPS-252766
**Related filings**
~- There are 642 continued-in in legacy companies for 2025 and none of them have filed amalgamation.~
~- Translated, opening the Continuation In in BCROS Prod will not create any additional issues.~
- of the companies that Continued In a significant number amalgamated or continued out subsequently
- of the Continued In companies that amalgamate the majority do so within the first month
- this highlights the need to launch Continuation In, Continuation Out and Amalgamation together
**Prod Deployment pre-requisites:**
- [ ] Receiving final UAT approval
- [ ] Business decision and announcement that BCROS will be the only environment for new Continuation In filings.
- [ ] Confirmation with Names unit team Continuation In NR's will no longer require consent.
- [ ] Have the filing's Feature Flags ready to be turned to On.
**Post Deployment Prod Scenarios mitigation:**
- [ ] User never used COLIN and user does not have BCROS account
- Create BCROS account
- Continue In
- [ ] User never used COLIN but user has BCROS account
- Continue In
- [ ] User has one or more COLIN companies
- [ ] COLIN companies are not migrated
- [ ] User does not have BCROS account
- Create BCROS account
- Continue In
- Migrate COLIN records to the newly created BCROS account
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.