-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corp number with restorations #6212
Comments
@Sienna-Blumstengel @lmcclung @janisrogers can this be looked into and requirements need to be documented. Ideally for next sprint. |
Verified this bug exists in TEST I also tested what happens if a client edits their name request in any way. The corp num does NOT disappear. Also, I tested what happens in name request after the corp num disappears. https://drive.google.com/file/d/1Aw8LDjJ8Sa4SMP-OoGI19kZkkU_R-cdL/view?usp=sharing
|
Need to review and update requestTypeRules.csv to see if the company number is a required field. The restoration related filing types: |
Can not build and install correctly in both local and openshift. Looks like python version problem. node-sass is supported by python 2 but we have python 3. |
The first step of the bug fix need to update requestTypeRules.csv and set Corp Num Required = TRUE for restoration requests. Also, the most hard part is upgrading webpack, node-sass and dependences etc upon to the error message in build process. The bug fix will be done after upgrade. |
DEV and TEST environments are ready to test. Steps:
|
Background
"For a NR that has been submitted for a restoration, for some reason, the incorp. number entered is being completely removed from the NR when we process it or make a change. I have two examples of this: 4468644 & 6375298"
The corp num is used by examiners for examination, it shows under the submit column.
Steps to reproduce
Expected behavior
screenshots
https://drive.google.com/file/d/1OGYLrCH9DThMYLAwllw_kA3m5tfVhm_3/view?usp=sharing
video of me replicating the bug
The text was updated successfully, but these errors were encountered: