Any updates on this?

This continues to bite us in the butt. Agents get tagged in the private channel on internal notes on something private and then reply thinking they are in a private context, only to have their private reply be crossposted publicly into Slack. I can't even choose to disable the private Slack channel as it's an invariant to having the integration going at all. It's extremely frustrating to have to police our agents to use an emoji lock when we all know it's super counterinuitive.

Thanks.

I would like to point out though that the workaround mentioned is not viable for us. We understand that we may have the option to also reply with the lock emoji for a private reply but we need this as default. Here are the reasons why:

1. The ability to have a default reply as private lowers the risk of information or data not being shared by accident. For example if someone accidentally doesnt select the lock emoji then it becomes a public reply and there could be critical data shared that was not supposed to be. This scenario has happened before also.
2. We have multiple teams that are non technical utilising replies in Slack. We have processes and guides built on these communications and by not having this as default it disrupts alot of the processes and guides we have in place.
3. We use JSM and Halp for customer comms and as a regulatory requirement we need to have a control in place to deflect situations that may result in accidental sending of data to external parties. The default lock emoji being in place for replies is that control and removing that setting now puts us at a breach in compliance.
    
   As you can see there are certain conditions in place that we need to meet and regulatory obligations we need to adhere to in our industry of Finance and collections. By Atlassian removing this it impacts us greatly. We cannot afford for these changes to go ahead and it may mean that we have to utilise another tool or look at moving off Atlassian altogether if that specific setting cannot be met.
    
   Can I please ask that you escalate this as a matter of urgency and I would like to talk to someone from the product team to understand why this setting is being removed at all and give my feedback directly. I can already see that the issue has 44 votes and increasing.
    
   It doesn't make sense for this top be removed from a customer level and the announcement about "Creating a more cohesive Assist experience in Slack" which is found in the link below dictates the entire sentence.
    
    https://community.atlassian.com/t5/Jira-Service-Management-articles/Creating-a-more-cohesive-Assist-experience-in-Slack/ba-p/2599364#:~:text=a%20request%20type.-,Agent%20replies%20now%20default%20to%20public,-Who%20does%20this 
    
   The term cohesive is defined as "consists of parts that fit together well and form a united whole". In no way is removing that setting cohesive for us at all, and if anything  its the exact opposite.

I do hope that this message does get to the right people. I would lastly like to remind you that our company currently pays for over $10k USD per month for Atlassian products and we are continuously growing which in future will increase the costs that you get from us. We are invested in Atlassian and what they are doing, all I ask is that Atlassian also invest in us and our requirement to keep this setting and not remove it.