1. Plan Upgrades and DataPacks purchased in APR
1% of the install base bought needed DataPacks and/or got Plan Upgrades, ie, 99% of installed customers were fine with the capacity allocated.
2. New Message Capacity
In APR we saw some larger customers onboard pushing the upper limits of what we had considered would be ‘the max’, so we’re upping the top end of the plan capacity range, which has a trickle down to all other plans, effective 1st MAY.
Plan | Previous MSG | New MSG |
Bronze1 | 3000 | 4000 |
Bronze2 | 4000 | 5000 |
Bronze3 | 5000 | 6000 |
Bronze4 | 6000 | 7000 |
Silver1 | 7000 | 8000 |
Silver2 | 8000 | 9000 |
Silver3 | 9000 | 10000 |
Silver4 | 10000 | 11000 |
Gold1 | 11000 | 12000 |
Gold2 | 12000 | 14000 |
Gold3 | 13000 | 16000 |
Gold4 | 14000 | 18000 |
Platinum1 | 15000 | 20000 |
Platinum2 | 16000 | 22000 |
Platinum3 | 17000 | 24000 |
Platinum4 | 18000 | 26000 |
Platinum5 | 19000 | 28000 |
Argon1 | 20000 | 30000 |
Argon2 | 22000 | 32000 |
Argon3 | 24000 | 34000 |
Argon4 | 26000 | 36000 |
Argon5 | 28000 | 38000 |
Argon6 | 30000 | 40000 |
Krypton1 | 31000 | 42000 |
Krypton2 | 32000 | 44000 |
Krypton3 | 33000 | 46000 |
Krypton4 | 34000 | 48000 |
Krypton5 | 35000 | 50000 |
Recently, JEMH Cloud had some trouble handling large amounts of Jira issue event data being sent in a small time-frame. These problems unfortunately resulted in unintended outages to Jira event processing and notifications of these events. The full post-mortem for this outage was posted here: https://thepluginpeople.atlassian.net/wiki/x/AYBCoQ .
This release improves the resilience of JEMH Cloud when high amounts of issue event data from Jira is received within a small period of time.