Comment Default Visibility for Jira – Setup Guide

This guide walks you through installing and configuring the Comment Default Visibility app on your Jira Cloud site.

1. Install the app

  1. In Jira, go to Settings (gear icon) → Apps → Find new apps (or Manage apps → Find new apps).
  2. Search for Comment Default Visibility (or Comment Default Visibility for Jira).
  3. Click Install and follow the prompts.
  4. Accept the requested permissions when prompted.

Screenshot: Capture: Jira Settings → Apps → search results showing the app, or the app’s install/configuration screen.

Jira Apps search or install screen

2. Open the configuration page

  1. Go to Settings (gear icon) → Apps → Manage apps.
  2. Find Comment Default Visibility (or Comment Visibility) and click it.
  3. The app opens its configuration page titled Comment default visibility.
Screenshot: The full admin configuration page showing Global default, Project overrides, Component overrides, and Backup & restore sections.
Screenshot: The full admin configuration page showing Global default, Project overrides, Component overrides, and Backup & restore sections.

3. Configure the global default

The global default applies to all projects unless overridden.

  1. In the Global default section, choose a Visibility scope:
    • Internal (Jira users only) – Only Jira users can see the comment.
    • Group – Only members of a specific Jira group can see it. Select the group from the dropdown.
    • Project role – Only users with a specific project role can see it. Select the role (roles are from your first project; for project-specific roles, use project overrides).
  2. If you choose Group or Project role, ensure the group/role has members. The app will warn you if it appears empty.
  3. Click Save at the bottom of the page.
The Global default section with the scope type dropdown expanded, showing Internal, Group, and Project role options.
The Global default section with the scope type dropdown expanded, showing Internal, Group, and Project role options.

4. Add project overrides (optional)

Use project overrides when some projects need a different default visibility.

  1. In the Project overrides section, click the Choose a project dropdown.
  2. Select a project that does not yet have an override.
  3. Choose the scope type (Internal, Group, or Project role) and, if needed, the group or role.
  4. Click Add override.
  5. Repeat for other projects as needed.
  6. Click Save.
The Project overrides section with at least one override in the table and the "Add override" form visible.
The Project overrides section with at least one override in the table and the „Add override“ form visible.

5. Add component overrides (optional)

Use component overrides when certain components should have a different default visibility than the project.

  1. In the Component overrides section, select a project from the dropdown.
  2. Select a component from that project (only components without an override are shown).
  3. Choose the scope type and, if needed, the group or role.
  4. Click Add override.
  5. Repeat for other components as needed.
  6. Click Save.
The Component overrides section with the project and component dropdowns
The Component overrides section with the project and component dropdowns

6. Backup and restore (optional)

You can export your configuration as JSON and import it later (e.g. after reinstalling or on another site).

  1. Click Export config to copy the JSON to the text area.
  2. To restore, paste JSON into the import field and click Import config.
  3. Click Save after importing.
The Backup & restore section with exported JSON visible in the text area.
The Backup & restore section with exported JSON visible in the text area.

7. Where the app appears in Jira

After configuration, the app shows up in these places:

LocationWhat you see
Issue sidebarA „Comment scope“ panel showing the effective default visibility for the current issue.
Issue panelAn „Add comment“ panel with a visibility dropdown and comment editor.
Issue actionsAn „Add comment“ action that opens a modal to add a comment with the default visibility.

Screenshot: Capture: An issue view with the „Comment scope“ panel visible in the right sidebar.

The "Add comment" panel open with visibility dropdown and comment editor.
The „Add comment“ panel open with visibility dropdown and comment editor.

The issue actions menu with the „Add comment“ action visible.

8. Scope resolution order

The app applies visibility in this order (first match wins):

  1. Component override – If the issue has a component with an override, that is used.
  2. Project override – If the project has an override, that is used.
  3. Global default – Otherwise, the global default is used.

If the user is not a member of the configured group or role, the comment stays public (no visibility restriction).

9. Troubleshooting

ProblemWhat to check
License requiredThe app requires a valid license. Check your Atlassian Marketplace subscription.
No groups/roles in dropdownThe visibility dropdown only shows groups and roles you belong to.
Comment failed: not a member of groupThe selected visibility (group or role) has no members you’re in, or the group/role is misconfigured.
Default not appliedConfirm the scope has members and that you’re in that group or role.
Admin page not foundGo to Settings → Apps → Manage apps and open the app from there.