V1.2.120 released

Created by Andy Brook [Plugin People] (Unlicensed)
Nov 21, 2016
1 min read

Summary

  • 21 Nov 

     JEMHC-1205 Error creating a new Email Notification Mapping

  • 20 Nov 

     JEMHC-1198 Notify customer when volume exceeds XX % of last 5 day average

  • 20 Nov 

     JEMHC-1204 Need to handle send fails when too many recipients re involved

  • 18 Nov 

     JEMHC-1199 Set run act user enabled by default

  • 14 Nov 

    JEMHC-999  Deprecation notice: remote conditions

  • 14 Nov 

    JEMHC-1194  Revisit permission for adhoc notifications using standard permission schemas

Highlights

Bugfix for creating new Email Notification Mappings

now fixed.

Notifying customer of excess notifications

We find from time to time customer get a runaway notification scenario, mostly we catch this and try to advise just-in-time, however, our first pass seems too spammy for smaller scale customers so we're redoing that.

Act As User has now been enabled in all profiles by default

To provide a more seamless commenting behaviour (in JIRA the comment creator will be the JIRA user associated with the sender of the incoming message, if it exists).  New Profiles have this enabled by default.  The ability to use this feature requires your addon descriptor to be up to date.  Access Manage Addons > JEMHC and use Update.

Ad hoc permissions now granted through custom permission in Project Permission Scheme

Due to the Deprecation (due for removal) of some underlying features used by JEMHC to manage permissions to access the "Ad hoc notification" feature, we've taken the opportunity to re-implement this in a more consistent way using standard JIRA project permissions.  From this point, you'll need to allocate the required permission, see the how to:  Use Ad hoc notifications#Access-Permissions – unfortunately due to this change, carrying over access permissions wasn't possible.