bcgov / bcgov/entity

Verify BN/MRAS/Orgbok messaging

Open
#4,323 0 comments 0 reactions 0 assignees View on GitHub
ENTITY - DO NOT USE STORY
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

## description
This ticket is to verify that the legacy app jobs / messaging still work after a correction is filed.
* Make sure **BN** messaging kicks off if **company name** has been corrected
* Make sure **MRAS** messaging kicks off if **any information** has been corrected
* Make sure **Orgbook** messaging kicks off if **company name, or entity type** has been corrected

Incorporate benefit company BC0879527
Do IA Correction
- [ ] Correct name (should trigger BN, MRAS, VON) - NR 1260566
- [ ] Correct Company Address (should trigger BN, MRAS)
- [ ] Correct Director (should trigger BN, MRAS)
- [ ] Correct company type?? - cannot test at this time?
- [ ] Correct share structure (shouldn't trigger anything? Maybe MRAS?)

- [ ] David, Robert, Linda, & Kial verify
- [ ] If there is work, Kial will make tickets and inform Linda/Kaine to estimate the tickets and prioritize

## Requirements document
[correction to a BComp Incorporation application](https://docs.google.com/document/d/1jom5rfmbgmntnFLRG1ecGOCsdnH_3XO3qWOuxl5nl3I/edit?usp=sharing)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked correction requirements document and the BN, MRAS, and Orgbook messaging paths; use benefit company BC0879527 and IA Correction to exercise the listed corrections. Done means the checklist outcomes are verified and any required follow-up work is recorded as separate tickets for estimation and prioritization.

Written by the indexing model from the issue text.

Assessment

Domain
backend, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.