LEAR/FILER : Different Temp filing for Same NR >>> One Filing Merge
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Describe the bug in current situation**
Currently, We have setup where One NR can create multiple Temp Filings.
Once any one of the filing gets Business Number, State for the NR changes to Consumed therefore, the other temp filings gets void and cant be converted to business anymore
**Link bug to the User Story**
https://dev.business-dashboard.bcregistry.gov.bc.ca/TuUgB9FgP1?filing_id=199082&accountid=3040
converts to business below:
https://dev.business-dashboard.bcregistry.gov.bc.ca/BC0888050?filing_id=199082&accountid=3040
https://dev.create.business.bcregistry.gov.bc.ca/incorporation-review-confirm?accountid=3040&id=TSA2mLXLIv
**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.
**Chance of Occurring (high/medium/low/very low)**
**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**
**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to Names >> Create NR >> Approve the NR
2. Go to BRD >> Find the NR >> register it ,leave it in the tab
3. Go to Names >> Manage My Name Request >> Fill Details >> Incorporate Now
5. Creates 2 diff temp filings
6. File one of them >>> Converts to business
7. Other temp stays in db as a Draft which cant be used
**Expected behavior**
delete the extra filing where nr is consumed, as this cant be used anywhere now.
This is to reduce the possible duplicates for the Org.
Possible Solution:
Filer can check if nr is consumed once business is assigned, delete any other related NR filings.
**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the flow through Names, BRD, and Manage My Name Request, creating two temporary filings for one approved name request and filing one. Trace where assigning the business number marks the name request consumed and where related filings remain as drafts. Done means the unused related temporary filing is removed and the filed business remains usable without duplicate filings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgres
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100