Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Just confirming what I think to be true.... with standard JIRA, there's no way to notify an outside person who is not a JIRA user about ticket updates, right?
Seems like you have to use ServiceDesk or Opsgenie for that, right?
Thanks
Hi Alan, in fact you can do this using Automation. There is an action to send an email and you simply add any valid email address you would like.
Of course they can't access the issue in the application but you can put as much detail in the email that you like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I confirm what @Jack Brickey said. Automation is the way to go, since Notification Scheme, although has the option to send email to individual person, it will only send for public issues.
Keep in mind that Service Desk will not notify the customer for all issue updates. Most of the time the customer will receive updates about the status, or about a comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the fast response! I'm sorry, I don't know what a Public Issue is, would you mind explaining (or pointing me to the doc? I did search help).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Public issues are issues which have a Permission scheme that gives the 'Browse Projects' permission to 'Anyone'(any non-logged-in users). You may read more about project permissions here.
As a workaround you could always forward your incoming mail to another person. However I would put some serious thought on this, prior of forwarding any email. And even if you do decide to do that, you have to setup your rule very carefully, so as to send only the necessary.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so thank you for the explanation! I don't think we'd want to use Public Issues. I really just want to notify someone external that a ticket has been updated (and send the updated comments).
I suspect ServiceDesk is a better out-of-the-box solution, was just trying to keep things simple by leveraging what we already have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agreeing with Jack and Alex on using automation rules...
Another work-around is to create a saved filter, subscribe to it so you get emails of the details, and forward that to others (perhaps using an email applications rules). The key differences between this and the automation approach are:
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.