Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,510
Community Members
 
Community Events
184
Community Groups

Normal users can make internal comments, how do I separate that?

I have a Service Desk project in which customers can actually comment using internal comment instead of normal ones.
Of course, to maintain different communications with internal team and the customers I'd like to have that separated. I have been looking but see no option for this, what am I missing?

1 answer

1 accepted

1 vote
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Hi @gcapdevila

portal-only customer accounts are not able to comment internally as a Jira Service Management license is required.

If you customers have an Atlassian account and product access to Jira Software, then they are able to make internal comments on a Jira Service Management issue.

The only way to avoid this is not to grant them the Browse Projects permission for that service project (within the permission scheme, either via group or role).

Hey @Dave Mathijs

Thank you so much for your answer. It clarifies how it works and why this was happening. Unfortunately this doesn't solve my issue, but still it is really helpful.

 

Thanks :)

Like Dave Mathijs likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events