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

Adjust ticket serializers must return fields as read-only if user lacks access #478

Open
2 tasks
Tracked by #560 ...
jon-nfc opened this issue Jan 21, 2025 · 0 comments
Open
2 tasks
Tracked by #560 ...
Labels
task::feature Adds functionality type::task Issue Type

Comments

@jon-nfc
Copy link
Member

jon-nfc commented Jan 21, 2025

Ticket permissions are custom and are at the field level.

Details

Based off of a users permissions mark fields as read-only if they lack the required permission for the field. This is required for the UI to make the required changes so as not to present the user with UI features they are denied permission from accessing.

note: users are already denied access from editing a field they dont have access to.

Tasks

  • Make serializer fields read-only if the user has no access to it.
  • Test
@jon-nfc jon-nfc added task::feature Adds functionality type::task Issue Type labels Jan 21, 2025
@jon-nfc jon-nfc added this to the Next Release milestone Jan 21, 2025
@jon-nfc jon-nfc moved this to Planning in Centurion ERP Jan 21, 2025
@jon-nfc jon-nfc moved this from Planning to Backlog in Centurion ERP Jan 22, 2025
@jon-nfc jon-nfc removed the status in Centurion ERP Jan 23, 2025
@jon-nfc jon-nfc moved this to Planning in Centurion ERP Jan 23, 2025
@jon-nfc jon-nfc removed this from the Next Release milestone Jan 26, 2025
@jon-nfc jon-nfc moved this from Planning to Backlog in Centurion ERP Jan 26, 2025
@jon-nfc jon-nfc removed the status in Centurion ERP Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task::feature Adds functionality type::task Issue Type
Projects
Status: No status
Development

No branches or pull requests

1 participant