Skip to content
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

NR expiry date is not being extended for future effective filings #23050

Closed
severinbeauvais opened this issue Aug 29, 2024 · 12 comments
Closed
Assignees
Labels
bug Something isn't working Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for. Names Team Name Request Name Examination Team NameX NameX and related services proxied via namex NRO NRO Replacement Priority1

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Aug 29, 2024

This used to work, but I've been testing with a FE continuation application and a FE incorporation application and it's not working right now.

This may be caused by #22931. apparently not

Example:

I created this NR, approved it, and set it to expire today (Aug 29 at 11:59 PM):

image.png

https://dev.namex.bcregistry.gov.bc.ca/transactions?nr=2516555

Then I filed this IA with a future effective date of tomorrow (Aug 30) at 7:30 AM:

image.png

https://dev.business.bcregistry.gov.bc.ca/T05aKXLl70?filing_id=150720&accountid=3040

My expectation is that the NR's expiry date would be extended to the FE date plus 1 extra day buffer. In this case, the new expiry date should be Aug 31 (at 11:59 PM). But I see no evidence of that.

PS The original ticket to extend the NR expiry is #3883.

@severinbeauvais severinbeauvais added bug Something isn't working Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for. labels Aug 29, 2024
@severinbeauvais
Copy link
Collaborator Author

severinbeauvais commented Aug 30, 2024

I have tested this scenario with an incorporation application and the results were the same (no evidence that the NR expiry was extended).

In other words, this bug likely applies to IAs, registrations, amalgamations and continuation-ins.

As such, I think the priority is higher than 3. What do you think? @vysakh-menon-aot @ozamani9gh @davemck513 @Mihai-QuickSilverDev

@severinbeauvais severinbeauvais added NameX NameX and related services proxied via namex Names Team Name Request Name Examination Team labels Sep 4, 2024
@severinbeauvais
Copy link
Collaborator Author

I tested this again today, and again the NR expiry was not extended as expected. @vysakh-menon-aot looked into it and believes something got changed in Namex API:

image.png

@ozamani9gh , @rarmitag , @eve-git , can you look into this? The impact is that the Entity Filer may not be able to mark a NR as Consumed -- the NR will already be Expired and we don't know if Namex allows consuming an expired NR. But we believe this will not stop a business from being incorporated with the correct approved name.

@eve-git
Copy link
Collaborator

eve-git commented Sep 4, 2024

I am reviewing the code change.
https://github.com/bcgov/namex/pull/1557/files#diff-568c1126b23759b7e43e19f04dc1c911ddc673039bec483f27394af5be5a454a

@eve-git eve-git self-assigned this Sep 4, 2024
@Mihai-QuickSilverDev
Copy link
Collaborator

@ozamani9gh @eve-git The NR upgrade to Priority appears to be broken. This is now a high priority.

@eve-git
Copy link
Collaborator

eve-git commented Sep 5, 2024

Ready to test in TEST environment

Besides the test case for incorporation (as described), please also include the test cases mentioned in #22243.

@severinbeauvais
Copy link
Collaborator Author

@eve-git Can this be tested in Dev environment?

@severinbeauvais severinbeauvais changed the title LEAR: NR expiry date is not being extended for future effective filings NR expiry date is not being extended for future effective filings Sep 9, 2024
@severinbeauvais
Copy link
Collaborator Author

severinbeauvais commented Sep 9, 2024

I have verified, in both Test and Dev, that the NR expiry date is extended to "1 day past the application's future effective date), as expected.

Still to verify: whether the NR is changed to Consumed when the applications are completed by the Filer (which will happen tomorrow at 9am). Verified! Here's the data from a previous test I did:

image.png

@severinbeauvais
Copy link
Collaborator Author

We moved this to Done in Entities-Olga's board because, as far as we're concerned, this is fixed.

We did not close this ticket because Names team needs to test/release/deploy it.

@Mihai-QuickSilverDev
Copy link
Collaborator

  • Tested. Moving to Ready for Release.

@Mihai-QuickSilverDev
Copy link
Collaborator

@ozamani9gh Would it be okay to close this ticket in the Entities space? Would it be captured okay in the Names space?

@ozamani9gh
Copy link
Collaborator

once you close it, then it closes the ticket on our board as well, leave it in done for their board, till we release it

@vikas-gov
Copy link
Collaborator

Release date to be confirmed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for. Names Team Name Request Name Examination Team NameX NameX and related services proxied via namex NRO NRO Replacement Priority1
Projects
None yet
Development

No branches or pull requests

6 participants