Skip to main content
← Back to list
01Issue
BugOpenSwamp CLIPublicTeam
Assigneesstack72

Relationships

#1312 Issue filing inherits most-recently-created collective's scope and privacy, with no way to choose

Opened by kneel · 7/21/2026

After creating a new collective and marking it private, all subsequent swamp issue bug and swamp issue feature commands file issues under that collective with private visibility — even when the issue has nothing to do with that collective.

The behavior appears to depend on the most recently created or joined collective, rather than the user's personal collective or an explicit choice. There is no flag to specify which collective context an issue should be filed under.

Current behavior

  • swamp issue bug and swamp issue feature file issues against whatever collective the system considers "current" (seemingly the last one created or joined).
  • If that collective is marked private, the issue inherits private visibility.
  • No CLI flag or prompt lets the user choose a different collective context at filing time.

Expected behavior

  • Issues should default to the user's personal collective unless explicitly scoped otherwise.
  • A flag like --collective <name> should let the user choose the filing context.
  • Privacy/visibility should be an explicit property of the issue itself (or inherited from a deliberate collective choice), not silently inherited from the most-recently-touched collective.
  • The CLI should make the filing context clear before submission (e.g., "Filing under @kneel (public)" or "Filing under @myorg (private)").

Why this matters

Users who create or join multiple collectives end up with issues scattered across the wrong scopes, sometimes with unintended privacy. A bug report meant for the public Lab ends up private and invisible to the team that could fix it. A feature request meant for a specific collective ends up filed against the user's personal namespace instead.

Steps to reproduce

  1. Create a new collective (e.g., @myorg) and mark it private.
  2. Run swamp issue bug --title "Test" --body "Test body".
  3. Observe that the issue is filed under @myorg with private visibility, even though the user's personal collective is @kneel.

Environment

  • swamp CLI version: 20260720.142822.0-sha.0caa5556
  • Platform: linux
02Bog Flow
◉OPEN○TRIAGED○IN PROGRESS○SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW

Open

8/28/2026, 12:21:26 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
kneel moved this from the private collective Elowish to public9/1/2026, 2:58:40 AM
stack72 assigned stack727/27/2026, 9:59:53 PM
stack72 marked as blocked7/28/2026, 2:50:39 PM
stack72 unblocked7/28/2026, 6:34:19 PM
Editable. Press Enter to edit.

kneel commented 7/21/2026, 3:01:27 AM

(This can be made public). Thanks!

Sign in to post a ripple.