Skip to content

feat(api/v2): adjust quarantined ticket visibility - #5172

Open
wescopeland wants to merge 1 commit into
masterfrom
stack/tickets/1-quarantine-visibility
Open

feat(api/v2): adjust quarantined ticket visibility#5172
wescopeland wants to merge 1 commit into
masterfrom
stack/tickets/1-quarantine-visibility

Conversation

@wescopeland

@wescopeland wescopeland commented Aug 16, 2026

Copy link
Copy Markdown
Member

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.

@wescopeland
wescopeland requested a review from a team August 16, 2026 20:36
@greptile-apps

greptile-apps Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Exposes quarantined tickets to authenticated V2 API consumers, matching website visibility.

  • Removes quarantine filtering from Ticket::visibleTo().
  • Updates index coverage for non-manager consumers.

Confidence Score: 5/5

The 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

@wescopeland
wescopeland force-pushed the stack/tickets/1-quarantine-visibility branch from 9669509 to 8034ec4 Compare August 26, 2026 23:16
@wescopeland
wescopeland force-pushed the stack/tickets/1-quarantine-visibility branch from 8034ec4 to ee599e2 Compare August 31, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants