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

Unable to Save Rule in OnCall Settings for User Profile #64

Open
AndiError opened this issue May 16, 2024 · 0 comments
Open

Unable to Save Rule in OnCall Settings for User Profile #64

AndiError opened this issue May 16, 2024 · 0 comments

Comments

@AndiError
Copy link
Owner

AndiError commented May 16, 2024

URL: https://my.dev.ringrx.com/v2/settings/users
User: [email protected]
Role: admin

Problem:
The system fails to save a Contact Rule added to the OnCall Settings for a user profile. Although the rule can be added to the tab(but the system add the previously added rules, looks like some cache but not from browser side), an error is displayed when attempting to save it. Subsequently, other sections after this error also fail to save, displaying the same error message: "Couldn't find PbxUserSchedule with ID=165 for PbxUser with ID=10994".

Notes: This issue occurs only when an admin attempts to create a rule for another user; it works correctly when an admin creates a rule for themselves.

Step to reproduce:

  1. Log in to the system with an Admin role user.
  2. Go to the Settings, under Avatar
  3. Navigate to Users tab
  4. Select "View" for any existed user.
  5. Go to the OnCall Settings section, and click on "Edit"
  6. Add a new rule to the user's OnCall Settings tab.
  7. Attempt to save the rule.

Expected Result:

The system should successfully save the newly added rule and display a confirmation message indicating that the rule has been saved.

Actual Result:

The system fails to save the rule and displays an error message: "Couldn't find PbxUserSchedule with ID=165 for PbxUser with ID=10994". Subsequent attempts to save in other sections also fail with the same error message.

Attachments:
https://www.loom.com/share/826253a3e85c4126af3ce656019d8ae6

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

1 participant