Skip to main content
← Back to list
01Issue
FeatureOpenSwamp CLITeam
AssigneesNone

Relationships

#964 Support confidential visibility for non-security issues

Opened by evrardjp · 7/4/2026

Summary

Users should be able to file an issue as confidential even when it is not strictly a security vulnerability.

Current behavior

The CLI has a dedicated swamp issue security path for vulnerability reports, but ordinary bug and feature reports do not expose a documented way to mark the issue as confidential at creation time.

Expected behavior

Provide an option to create bug or feature issues with confidential visibility, for example swamp issue bug --confidential or swamp issue feature --confidential. Security issues should remain confidential by default, but non-security issues should be able to opt in to confidential handling when they contain private data (they mostly should not, but it can happen)

Why this matters

Some reports require private data to be useful, such as internal identifiers, private repository names, customer-specific details, logs, paths, or reproduction context. Users may avoid including enough information to diagnose the problem because they do not want to leak private information publicly. A confidential option would let them provide actionable details safely without mislabeling the report as a security vulnerability.

Suggested behavior

  • swamp issue security remains confidential by default.
  • swamp issue bug and swamp issue feature remain public/non-confidential by default.
  • Bug and feature reports can opt in to confidential visibility.
  • The CLI should make the visibility clear before submission and in JSON output.
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

7/4/2026, 10:57:39 AM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.