nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sending external comments over email through automation

Erik George

Hello,

I have an automation rule created in Jira that sends comments to reporters (one sending the most recent one, and another that sends all the comments on the issue). However, I recently noticed that this includes internal comments as well. Is there a way to make it so only non-internal comments are sent?

Thank you!

Accepted answers

Stefan Salzl

Hi @Erik George ,

I‘m sorry but can‘t follow your description. Isn‘t that the main functionality of jira seevice management that the reporter is notified via email about a new comment and furthermore the main functionality of internal comments that they are not sent to the customer and only shared between agents?

There shouldn‘t be an automation rule needed for that. This sounds like something that is configured in the notification settings.

Or did I get something wrong? If so could you please further specify your use case more detailled?

Best
Stefan

All comments

Stefan Salzl

Hi @Erik George ,

There shouldn‘t be an automation rule needed for that. This sounds like something that is configured in the notification settings.

Or did I get something wrong? If so could you please further specify your use case more detailled?

Best
Stefan

Erik George

The default email notifications to reporters is turned off for us and instead we have custom automation rules in place that send the reporter both the latest status and comment whenever there is a status change, as well as giving the reporter the ability to request full details of the ticket (via email rather than the portal) that provides more information as well as the entire comment history.

My problem is that this also sends internal comments to the reporter. I think there's a smart value for comments.internal - but is there anything that is the opposite, and just selects external/non-internal comments?

Stefan Salzl

May I ask why the standard notification is turned off? It gives exatly the information you would like to have (status and comment via email, excluding internal comments).
imho I would rethink the idea of turning off native functionality and try to implement exactly the same thing with automation.

furthermore:
what does "full details of ticket" exactly mean? What kind of information does the user get?

Anyways:
How do you collect the data (comments) that should be returned to the user? Could you show your automation rule/how far you´ve gotten and where you got stuck?

Best
Stefaen

Erik George

That's a good question that I don't exactly have the answer to. I was given control of the project about 80% into it's development, with all of the notifications being based around automation rules. Resolutions, status updates, ticket creation, etc. - so that's just what I went with.

For the full details, the rule displays the ticket creation date, current status of the ticket, the last time it was updated, and every comment on the ticket.

For comments, I just use {{#issue.comments}} (as well as author & date), but it also collects internal comments.

Thanks!

Screenshot 2022-09-06 083909.png

Jeff Pittman_jaqbof

I only want the LAST Public Comment to be included in the Notification. The use case is that not every participant is opting into Notifications. So, the team wants an override Automation, of sorts, to eMail comments to the Reporter and the Participants with the Last Public comment Made.

Trigger: Comment is Main Action

Condition: Comment is Public

Action: Send eMail w/ Last Public comment, and include other issue details.

I can get ALL the public comments to send, however it's also triggered IF any Comment (internal or external) is made...then it just excludes internal comments and adds all the past external comments into the eMail.

I just want the Last Comment, and it not to send if the COmment was Internal via Automation for Jira.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

comment

automation

external

internal

jira-service-management-cloud

jira-service-management