feat(api/v2): adjust quarantined ticket visibility - #5172
Open
wescopeland wants to merge 1 commit into
Open
Conversation
Contributor
Greptile SummaryExposes quarantined tickets to authenticated V2 API consumers, matching website visibility.
Confidence Score: 5/5The PR appears safe to merge. The visibility change matches the stated API behavior and existing website access. Reviews (1): Last reviewed commit: "feat(api/v2): adjust quarantined ticket ..." | Re-trigger Greptile |
Jamiras
approved these changes
Aug 18, 2026
wescopeland
force-pushed
the
stack/tickets/1-quarantine-visibility
branch
from
August 26, 2026 23:16
9669509 to
8034ec4
Compare
wescopeland
force-pushed
the
stack/tickets/1-quarantine-visibility
branch
from
August 31, 2026 20:22
8034ec4 to
ee599e2
Compare
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
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.
I changed my mind on a V2 API implementation detail.
Quarantined tickets are now exposed through the V2 API regardless of the consumer context. This makes the API consistent with the website UI.