Restricting Comment Permissions for Specific User Group

[Rajesh_Kumar]

Hi Team,

I need assistance with implementing comment restrictions for a specific group of users across selected projects.

Requirement: A group of users needs to be restricted from adding comments on tickets in selected projects, while retaining their ability to view those tickets.

Current Situation: Upon reviewing the users' permissions and group memberships, I found that:

• These users are members of the default group and their respective departmental groups
• Most of the target projects utilize the default group in their permission schemes
• Some projects use selective groups, and these users are members of those groups as well
• Removing users from these groups would impact their access to other projects where they require full permissions

Attempted Solution: To avoid modifying existing groups and permission schemes, I implemented the following approach:

1. Created a new group called "CSM_NoCommentAction"
2. Added the target users to this group
3. Modified the project workflow by adding workflow properties:
   • Property Key: jira.permission.comment.denied
   • Property Value: group:CSM_NoCommentAction

Issue: This configuration blocked commenting for all users across the project, not just members of the CSM_NoCommentAction group.

Request: Could you please advise on the best approach to achieve this requirement without affecting existing group memberships and permission schemes? Specifically, I need to:

• Restrict commenting permissions for specific users in selected projects only
• Maintain their view access to tickets
• Preserve their existing permissions in other projects

Thank you for your assistance.

[Tomislav Tobijas]

Hey @Rajesh_Kumar ,

I believe this is what you are looking for: JRACLOUD-80510: Ability to restrict comments to exclude visibility for a set of groups or Project roles 

There is no happy solution here, but what you could do is reconfigure the permission scheme a bit and restrict commenting by space role or group.
You could create something like "Can Comment" space role and then grant "Add Comments" permission only to this role + assign all users/groups who should be able to comment to this role in each project. 🤔

Hope this helps.

Cheers,
Tobi

[Jonas Nilsson]

I would avoid deny-style workflow properties for this use case. The cleaner pattern is a dedicated project role like "Can Comment" and then grant "Add Comments" only to that role in the permission scheme. That preserves view access while keeping comment rights scoped per project.

Separate point for later cleanup: once group and role references start spreading across permission schemes and project roles, reviewing impact gets tedious fast.

Disclosure: I work on Group Impact Audit for Jira. It is a read-only Jira Cloud app that shows exact group references in permission schemes and project roles before cleanup and lets admins export evidence. It does not currently scan filters, dashboards, issue security schemes, notification schemes, automation rules, or app-specific permissions.

Marketplace listing: https://marketplace.atlassian.com/apps/3693921448

[Shalini Pradhan]

Hello @Rajesh_Kumar ,

Good day! Welcome to Atlassian Community :)

Incase you want to restrict users from adding comments

• First create a user group and add the users who should not be adding the comment
• Add that user group under Browse project permission
• Then remove those users from default group
• Make sure the new group is not added under Add comment permission in the same space/project

Thank you