Skip to:

Marketplace

Notification Assistant for Jira - Email

works with Jira Cloud, Jira Server 10.4.0 - 10.6.1, Jira Data Center 10.4.0 - 10.6.1 and more

OVERALL RATINGS

INSTALLS

1,404

TRUST SIGNALS

We no longer offer sales and support for server apps. You can stay connected by exploring the migration options to either the cloud or Data Center version of this app.

Explore migration program

Reviews for server

3.7/ 4

Based on 35 out of 0 reviews across hosting types

Review guidelines

Our new review guidelines ensure that all the reviews are submitted by actual users of the app...

Showing 35 reviews

  • IT Admin

    Posted on Sep 12, 2017

    Very flexible, configurable, powerful, and easy to use add on. Invaluable for any sort of scheduled checks and notifications. Exactly what we needed - great value and highly recommended!

    Was this review helpful?
  • John Desha

    Posted on Aug 7, 2015

    This is a great add-on, very full featured and works as advertised. Riada is extremely responsive and has implemented feature requests for us in surprisingly short time. We are very impressed.

    Was this review helpful?
  • Piotr Cirf3

    Posted on Aug 28, 2020

    Who can create/configure a new report? Only admin or every user?

    Was this review helpful?
    • Modus Create

      Admins can configure regular notifications to be sent based on events or schedules.

      Admins can also configure Templates.

      Individuals can send out single issues using the Admin configured Templates.

  • Pavels Avens

    Posted on Mar 14, 2018

    It is a good ad-on, but there are some critical issues: 1. All datetime fields are being returned in Server time. There is no way to set Local time for datetime fields. 2. There is no possible to format custom fields (for example as Java SimpleDateFormat) 3. Notification does not work well with custom JQL functions. There is a bug in the add-on. The add-on will not work on CRON event if a custom function uses JiraAuthenticationContext to get currently logged in user, which was passed to SearchService. When running the add-on manually, there was a logged in user in current session. So there were no problems with custom functions. But when a custom function is being called by the add-on, JiraAuthenticationContext has no logged in user. We have resolved it by passing a user from JQL custom function QueryCreationContext. But there will be a problem with other custom functions. Therefore setting the currently logged in user inside the add-on will be a good solution.

    Was this review helpful?
    • Modus Create

      Hi Pavels,

      Thanks for reaching out. A few comments on your issues:

      • 1. This is a good idea and something we could implement and we'll update the ticket NAS-54 once implemented.
      • 2. The custom fields (like Date fields) are returned by the system date format so changing this format, will affect the output accordingly.
      • 3. This one is already implemented in the product. You can select the user to “run as” in each configured notification.

      If you have any other feature requests, just create or vote on tickets in our system.

      Best Regards //Team Riada

  • Kathleen Buckley

    Posted on Feb 11, 2020

    I contacted the vendor after I found a problem with the 'sender email address'. They figured out what the problem was and updated their app within days. Really fast fix and much appreciated.

    Was this review helpful?
  • Learn and explore

    • What’s Marketplace
    • App installation
    • About Atlassian
    • Atlassian resources
    • Search and ranking
    • Atlassian events
    • Atlassian foundation

    Follow