Hi all,
In Jira Cloud, it is possible to reply to a ticket via email. If I write an internal comment using an @mention and the recipient replies via email, the reply to the internal comment is treated as a public comment in Jira Service Management.
That shouldn’t be the case! I would regard that as a genuine security vulnerability.
Can I stop that from happening?
Thanks for any help!
Hello @Clemens Kleibusch
I do not think there is a native way to fully prevent this in JSM Cloud today.
If someone replies by email, that reply is treated as customer-facing communication, so I would not rely on @mentions in internal comments for sensitive discussion.
The practical solution Today are to keep that collaboration inside Jira only, move it outside the ticket, or use automation as a workaround to switch those comments back to internal. Atlassian already has an open feature request in this area.
https://jira.atlassian.com/browse/JSDCLOUD-3499
PS: Take a look on this App https://marketplace.atlassian.com/apps/1220666/jira-cloud-for-outlook-official
Hello @Arkadiusz Wroblewski
Thank you for your answer and the link to the ticket.
The workaround in the issue is easy to implement and at least I can use it to correct the incorrect permissions. But of course I can’t remove the notifications sent to customers, because that’s the most important piece of information for them – that they’ve received a reply!
Well, the ticket is only 10 years old, so I don’t want to be impatient...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello again,
It seems impossible to me to identify the comments in question. I couldn’t find anything that marked the comment as ‘sent by email’. Because those are the only comments I want to make internal, provided a suitable role can be found for the sender.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One important caveat for this workaround though: this only changes the comment visibility in Jira afterwards. It does not undo any customer notification that may already have been sent.
For that to work Stable and on Confident level will be needed from you to rely probably on some external Apps/Mailhändler
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Arkadiusz Wroblewski
Yes, I am aware of that caveat.
That is why I am considering disabling email replies in cases where no email channel has been set up. Das kann ich tun, indem ich eine ungültige Adresse angebe. Oder gibt es eine Möglichkeit das Verhalten projektweise abzuschalten?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo,
ja, wenn du das projektweit unterbinden willst, würde ich nicht mit einer ungültigen Mailadresse arbeiten.
Der sauberere Weg ist, den E-Mail-Kanal im Projekt zu deaktivieren unter
Project settings → Channels & self service → Email.
Wichtig ist dabei aber:
Damit verhinderst du dann nicht nur Antworten auf interne Kommentare, sondern den kompletten E-Mail-Kanal für dieses Projekt. Das muss dir bewusst sein.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo Arkadiusz,
so ist's einfacher :D
In den meissten Projekten habe ich keinen E-Mail-Kanal aufgesetzt. Nur durch Zufall habe ich nach der Migration in die Cloud festgestellt, dass Antworten auf eine Benachrichtigung auch ohne E-Mail-Kanal funktioniert.
Danke nochmal!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Aber gerne 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.