Repository navigation
fix(audits): use dedicated ticket audit permission - #5823
Merged
Merged
Conversation
3 tasks done
|
w940853815
approved these changes
Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use
audits.view_ticketauditfor the ticket audit menu, list route, and export action. This aligns the UI with the dedicated Core permission and removes the incorrect dependency on job audit access.Requires the Core permission migration in jumpserver/jumpserver#17676. Fixes TAPD 1077180.
Validation: full frontend lint and the production build passed using Node 24 and the installed tools; the local role permission tree and ticket audit list were verified. No test files or unrelated changes are included.