Skip to main content
← Back to list
01Issue
BugShippedSwamp ClubPublicEnterprise
Assigneesstack72

Relationships

#3602 Lab issue visibility: removing private status works, then label errors "You are not in a private collective"

Opened by tagur · 10/19/2026· Shipped 10/19/2026

PR #1371: https://github.com/swamp-club/swamp-club/pull/1371

Summary

On an issue in a private Enterprise collective, the "private" link removes private status. The issue then shows public. Clicking the visibility label shows "You are not in a private collective."

Setup

  • Collective plan: Enterprise
  • Collective setting: private
  • Visibility setting: "Hide all lab issues by default"

Steps

  1. File a new issue (#3597).
  2. Click "private" on the issue and remove the private status.
  3. The issue now shows public.
  4. Click "public". The message "You are not in a private collective" appears.

Also seen

Older issue #3396 is still listed as private. Clicking its label shows the same message.

Expected

  • The collective is private, so the membership check should pass.
  • The visibility toggle should work in both directions.

Actual

The toggle reports the user is not in a private collective. Collective settings still show private.

Suspected cause

The visibility check may read the wrong collective. It may not recognize the Enterprise private collective.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 8 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

10/19/2026, 5:27:29 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
tagur moved this from the private collective Two Nines to public10/19/2026, 3:23:45 PM
stack72 assigned stack7210/19/2026, 3:16:07 PM
Editable. Press Enter to edit.

system commented 10/19/2026, 3:14:49 PM

Classified automatically when this issue was filed.

  • Source: Swamp Club

If you feel this classification is incorrect, add a ripple to tell us so.

stack72 commented 10/19/2026, 5:27:36 PM

Thanks @tagur for reporting this! We shipped: Fix in the swamp-club repo. Lab list pages (/lab and /lab/) pass an empty viewerCollectives list to LabShell, so an issue opened from a list shows no Private option and says You are not in a private collective. Fill the list from listUserCollectivesWithRoles (the query the audience PATCH authorizes against) on every Lab page, and have the server send canChangeAudience with each issue detail, using the same rule as the PATCH, so the control is clickable exactly when a change will be accepted.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.