1 way issues will be created in our JIRA, are through sending an e-mail. Users in JIRA automatically recieve a notification that the issue is created. (Thanks to a little checkmark ;-))
BUT e-mail from people that are not users, don't get a notification.
I don't want all the people in the company to be a user, so how can I arrange that they do recieve an e-mail?
AND: I think I'd also like them to recieve the same notifications as the others (comments, start progress etc) or at least when the issue is resolved/closed including a comment.
Thank you, that looks really good!
I also checked out Email this issue (https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue) and I think the difference is, that this last tool can do more than only sending notifications right?
You can run any valid JQL query but we haven't provided any examples.
The syntax for JQL is pretty straight forward and the full reference documentation can be found here. Play around with JQL in JIRA and see the results in the Issue Navigator to get familiar with JQL, it will probably only take you a couple of minutes to get started. For more advanced queries, see the syntax on the reference page.
Ok I have read it and thought about it. Searched it for scripts with "user".
I begin wondering if this works for when people E-MAIL to Jira like it's with our Jira... : Because when the e-mailer is no existing user, it sets the reporter to a specific person, so I thought you would have "lost" the e-mailaddress from the sender at that point...
So I can't think of a JQL-script what could do the trick then............. help?!
So you have configured the incoming mail handler to replace the original sender's email address with a user that you have in JIRA. And the email handler does not create an account in JIRA for the sender. This means that you are not storing the senders email address anywhere in JIRA and you probably don't know exactly who is going to send emails to your incoming mail handler. Right?
I agree that you can't create a JQL query under these uncertainties.
If you on the other hand know (external email address) who is to be notified during certain circumstances (regardless of sender), then NAFJ can be a good choice for you.
Have you taken a look at JEMH?
That add-on can store the senders email address in a custom field allowing you to run sucessful JQL's whithout creating a JIRA account for the sender.
Yes, you are right. Because I don't want every emailer signup for JIRA because of our licence-limit. Good to know that NAFJ doesn't work for that.
JEMH is a bit over our budget, so I think the only option now is the add-on "Email This Issue". Maybe you know some helpful websites for that?
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs