Its been a little whilst since the 1.0.137 released was done, this has been mostly due to the development of new features, here are the highlights!
psst, if you missed the last post, small to mid tiers have had a Plan message count increase.
New Features
Ad hoc notification support
Just like JEMH (for JIRA Server), In JEMHCloud its now possible to create a notification directly from a JIRA issue, using canned responses, and/or customized content, as well as attaching pre-existing issue attachments. Issue Update by means of adding a comment to the related issue (with visibility level) is also supported.
The launch icon is the mail icon between the standard Share and issue export icons:
Below is a screenshot of the popup editor, for more detail see the wiki Use Ad hoc notifications.
Signature image detect
When signatures are sent in HTML, where body content is cut on comment, an attempt is now made to locate a remove images that are in the 'cut' part of the message, such that they do not get added to issues.
Localization of field values
Its now possible to localize the field values, eg 'Blocker'. See Translation of Values in Localize Templates.
Those 405 errors
Admins will have seen 405 error messages listed in the JEMHC console, there were largely spurious and ignorable, now JEMHC will have to be offline for several minutes before any such notification is made.
License history chart performance
The historical usage charts within the JEMHC > Licensing section were sub-optimal in the amount of time taken to create the chart, now they are optimal !
Forward user / inbound mailbox match check
If you were to setup the forward address the same as your inbound mailbox a mail loop would result (bad), the outcome of that would be the complete consumption of your months Plan. We've added a check in the Profile self-test (so please read those!)
Tagging Outbound mail with a common subject prefix
This has now been added, set via JEMHC > Messaging > Outbound > your entry : Subject Prefix
Licensing Issues
It came to light that the Marketplace license system isn't airtight and enabled repeat evaluations beyond 60days. Evaluation use is now only possible once with Marketplace evaluation licenses being valid for at most 30 days + remainder of current licensing period, at which time the evaluation will be invalid. In this state, no events will be stored, in JEMHC , no outbound emails will be sent, no inbound mail received. In such a state, accessing the JEMHC console will show:
Once evaluation is over, the only appropriate license state is Active, to address possible gaming scenarios. Enforcing the fair use of JEMHC for a single Evaluation Period, Hosts found to be obtaining free use beyond their permitted Evaluation Period may have their hosts access to JEMHC voided, with such hosts seeing the following, regardless of what Marketplace license is installed (unvoiding hosts can only be done through JEMHC support staff!)
Plans have not been changed since NOV 2014, there have been only a few customer who have exceeded Plans, usually by message count, so from JUNE 2015, the following plan changes will apply:
| Plan | Previous Msgs | From June Msgs |
|---|---|---|
| Guppy (10) | 500 | 500 |
| Clownfish (15) | 750 | 800 |
| Tetra (25) | 1000 | 1250 |
| Piranha (50) | 1500 | 1750 |
| Octopus (100) | 2500 | 3000 |
| Marlin (500) | 5000 | 5000 |
| Shark (2000) | 10000 | 10000 |
| Whale (unlim) | 16000 | 16000 |
This results in a distribution as shown:
Future changes for plan exceeded scenarios
Currently, when Plans are exhausted, JEMHC continues to generate outbound notifications (being nice!) but, that actually occurs indefinitely, which could result in mass email generation that could be detrimental to the JEMHC service. An upcoming release will address that, to provide a limited period where outbound notifications will work (e.g. 10% arbitrary level beyond Plan) before they too are stopped After that point, events will be queued for delivery, for a time. We still have to work out the detail but expect the implementation will be adequate for anyone in this situation.
Checking your Plan Usage
Use JEMHC admin, check the Licensing tab for a view of current month usage:
See your history usage over the last month with the report under the above, the annual trend is particularly useful to illustrate trends in your usage (ie constant, or UP UP UP!)
What Plan do you have?
See the Plans page
Who gets notified when of Plan consumption
You can manage who gets notified at a nominated usage level, as well as on complete use:
What to do when a Plan is exhausted?
When your Plan allocation is used up because there was an uncharacteristic bump in your usage. To recap there are two get-outs for plan exhaustion:
- Use a DataPack, for short term volume increase
- Get a Plan Upgrade, these are only available as a one off advance annual upgrade, regardless of subscription status.
See App licensing for more.
Today the following email was sent to some long-term evaluators of JEMHC, the period of which exceeds the expected Marketplace evaluation period of 60days. Simply, an Active license will be required after 60days of initial evaluation, regardless of any previous invalid/active/cancelled status. Hosts not playing fair will be voided, blocking all access to JEMHC.
Hi there!
You are receiving this email as current longer term evaluators of JEMHC. Regarding the evaluation period: The Atlassian Marketplace entry for JEMHC has a Pricing FAQ "can I extend my free trial":This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the add-on.Our records show your evaluation has been exceeding that, due in part to a flaw in the Atlassian marketplace licensing which is not enforcing this in all circumstances. Some hosts have evaluations starting back to January who still haven't actually paid a single $ :'(An Active license will soon be mandatory to continue to use JEMHC once your elapsed period (since initial eval) has exceeded 60days. Further eval installations will be blocked within JEMHC, regardless of Markteplace license status.Evaluators that are seen to continue their free-use period beyond 60days by any means could face being voided, which will result in immediate loss of all JEMHC services for your host, regardless of Marketplace license status. More info on voided licenses at:We want you to be happy with email services JEMHC provides, if there are problems, reach out to support via email to:If your evaluation was a success and you intend to drop onto a paid subscription, that's awesome, and you can just forget about this!If you have questions regarding anything here, feel free to reply!Best Regards,Andy
Hi there! The upgrade over the 9-10 May could have resulted in a problem that may not be immediately apparent. If the Webhooks Addon is disabled, then JIRACloud will not issue Events that JEMHC can hook into to generate notifications. If JEMHC Admin > Auditing > Events is showing traffic in the last 24hrs your instance is fine. See the following link for more:
This was a small release:
- Improve clarity of Report by referring related issue KEY for cases where comments cannot be made due to lack of permissions. This will help locate 'why' (e.g. mail thread association with another issue etc)
- Some users outbound SMTP servers don't default to a any particular From: address, meaning that Forwarded messages cannot be sent. In this release, the pre-existing Message Outbound address "Sender Email Address" field is now used as the from address, if present, for forwarded emails.
- Reduce JEMHC admin screen 40x error messages, they represented a single ping/operation failure to the back-end. Now, 3 consecutive fails are required.
there were some minor bugs in 1.0.144 that were worth re-releasing:
- Wizard wasn't correctly noticing existing custom fields on first load (needed refresh /first use)
- 40x errors in the header were too frequent, occurring on a single failed 'ping' to the backend, now requires 3 consecutive fails (3 minute downtime) before appearing.
In this release;
New features
- JSD Request Participants field supported as a target for email recipients who have JIRA accounts (requires workaround user defined to email -> user lookup), currently its not possible to 'use' request participants, will be added soon.
- Foreign Key association with issues can now be restricted to issues in a given status (eg resolved, closed)
- Field values can now be localised, eg value of 'Priority' being 'Blocker' could be translated to something else 'Level 1' for example.
- Its now possible to just enable "Use Reprocessed Message" to resolve some structural errors in received emails (this is a Profile level configuration, Profile > Edit > Pre Processing Tasks > Use PreProcessed Message: ON), for more see How To Use Pre-Processing Tasks.
Bugs Fixed
- JEMHC-408 Wizard driven Profile creation bug fixed
- Comments made with group-level security are now correctly detected and not mailed to email participants
Improvements
- Connection error messages are being sniffed, as most come from a set of mail providers, enabling links to related knowledge base articles to be given