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

Can't submit new contact or new operation #2624

Closed
pbastia opened this issue Dec 19, 2024 · 9 comments
Closed

Can't submit new contact or new operation #2624

pbastia opened this issue Dec 19, 2024 · 9 comments
Assignees

Comments

@pbastia
Copy link
Contributor

pbastia commented Dec 19, 2024

Describe the Bug:

A user can't submit a new contact or a new operation in the registration portal.

Developers:
There are errors thrown by RJSF on those forms, that the anyOf in the schema is not being properly used.

Reporting might have a linked error: bcgov/cas-reporting#434

Probability: 5

Impact: 5

Bug Matrix

Steps to reproduce the behaviour:

  1. Login as an industry user with no prior operation/contact (for instance bc-cas-dev-secondary or bc-cas-dev-three)
  2. Create a new operator
  3. Create a new contact or operation
  4. Hit submit
  5. Nothing happens

Screenshots:

New Operation:
Image

New Contact:
Image

Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional Context

  • Same behavior in both TEST and DEV environment
@pbastia
Copy link
Contributor Author

pbastia commented Dec 19, 2024

@fviduya 👀

@fviduya
Copy link
Contributor

fviduya commented Dec 19, 2024

Updated the issue description, added screenshots, issue exists on both DEV and TEST environment.

@Sepehr-Sobhani
Copy link
Contributor

I couldn’t replicate the issue locally or in the DEV environment. Maybe it’s already resolved? 🤔

@fviduya
Copy link
Contributor

fviduya commented Dec 30, 2024

Hmm, I was able to replicate it still on both dev and test envs. I used bc-cas-dev-secondary in DEV and created an operator (successful), then created an operation (unsuccessful, logs on console). On TEST env, I used bc-cas-test and got the same result.

@patriciarussellCAS
Copy link

Is this a separate issue to ticket 463 in Reporting?

@pbastia
Copy link
Contributor Author

pbastia commented Dec 30, 2024

@patriciarussellCAS it's the same, I believe. This one also mentions the Operations form, the cause is very likely the same

@Sepehr-Sobhani
Copy link
Contributor

Hmm, I was able to replicate it still on both dev and test envs. I used bc-cas-dev-secondary in DEV and created an operator (successful), then created an operation (unsuccessful, logs on console). On TEST env, I used bc-cas-test and got the same result.

Thank you @fviduya! I was able to replicate the issue with bc-cas-dev-secondary. The problem occurred because this user had no prior contacts or operations, unlike bc-cas-dev, which already had some contact/operation instances. This discrepancy was why I initially couldn't reproduce the issue. I’ll update the acceptance criteria for the bug ticket accordingly.

@patriciarussellCAS
Copy link

Test in Dev confirmed that I could create a new contact and create a new operation (but the operation did NOT show up in the Operations table - which is a separate bug that @Sepehr-Sobhani will create).

@Sepehr-Sobhani
Copy link
Contributor

Test in Dev confirmed that I could create a new contact and create a new operation (but the operation did NOT show up in the Operations table - which is a separate bug that @Sepehr-Sobhani will create).

Created a ticket to capture this bug: #2659 (However this issue is part of the bigger issue: #2590)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants