How pricing
Like other Atlassian cloud apps, JEMH Cloud'sworks
App pricing is based on the actual number of users in your Atlassian product. For example, if you have a 27 user Jira Software and a 10 agent Jira Service Desk, you pay the 27-user app price.
Your subscription grants you a usage allowance (called a "plan") which is based on the number of users that your subscription covers. Additional capacity can be purchased in the form of Data Packs, and Plans can be upgraded to higher tiers if needed.
Data Center to Cloud
We support Data Center customers with Dual Licensing (a fee DC license),where >1000 cloud seats are purchased for a year term in advance.Server to Cloud
JEMH for Jira Server is not paid through Atlassian Marketplace and is no part of the Dual Licensing path. As Server licenses are perpetual, they can of course continue to be used indefinitely for versions released in your maintenance window. Contact sales@thepluginpeople.com for more info.
Academic & community licensing
JEMHC follows Atlassian's cloud app licensing policy for Academic and Community pricing. In line with the basic subscription discounts, JEMHC Data Packs and Plan Upgrades are also available at a 50 % discount (the online shop does not handle Academic & Community discounts, you must contact sales@thepluginpeople.com for a quote).
Quoting & purchasing
We do not quote for cloud subscriptions directly. Instead, generate a quote via Atlassian. Per-user pricing can be found on the JEMHC Marketplace entry.
About data
JEMHC Email Usage is reset to zero on the first of every month. The metrics JEMHC Plan’s cover are based on Email Messages (count) and Data (MB) that include both Incoming mail retrieved by JEMHC and Outgoing mail sent by JEMHC, illustrated below:
1 Email in = 1 message, 1 Email out = 1 message (100 messages in with 200 messages out = 300 messages used)
1 Email of 10MB = 10MB of data in, 1 Email of 10MB out = 10MB of data (100 messages of 20MB = 2000MB of data used)
Free notifications that are not billed /counted involve low data/impact services like web-driven SMS and Instant Messaging notifications.
Why isn't unlimited usage part of the subscription fee?
While we would love to give customers unlimited usage capacity, this is not feasible in reality. Some customers require much higher capacity than others, and that capacity comes at a cost. For now, we believe the fairest solution is to use Plans.
A Plan grants a customer a certain amount of messages and data every month (on the 1st of each month). If you reach your plan's limit, your service stops until you top-up with a Data Pack, or the next month begins. Some users want messages, while some users want data. We try to balance plans so that there is something for everyone - sometimes this means the suggested plan is not suitable for you. In this case, most likely you'll need a Plan Upgrade. Plans are not intended to be a cash generator - they are a way of controlling excessive use by the few.
License types
All pricing here (and the e-junkie shop) are for commercially licensed instances. Discounts can only be acquired by emailing our sales team. Purchases are final and non-refundable. See https://developer.atlassian.com/platform/marketplace/app-discount-programs/ for comparison of subscription cost discounts. The following discounts apply for Plan Upgrades and Data Packs:
Type
Discount
Academic
50%
Community
75%
Classroom
75%
Open Source
75% (not free)
Per-User pricing
If planned capacity is exhausted, related top-up purchases are required to continue processing, this cannot be done through Marketplace and must be done directly through the shop or sales@thepluginpeople.com (see Data Packs and Plan Upgrades below), we do not do plan upgrades prior to payment.
correct as of 19 MAY 2021
Users
Monthly rate
Max (monthly)
Max (annual, 10 months)
Up to 10 users
$5
$5
$5
1 - 100 users
$2.5
$250
$2500
101-250 users
$250 + (users-100) * $1.50
$475
$4750
251-1000 users
$475 + (users-250) * $0.50
$850
$8500
1001-5000 users
$850 + (users -1000) * $0.50
$2850
$28500
5001-10,000 users
$1450 + (users -5000) * $0.50
$5350
$53500
Xenon /Radon Plan tiers are for discussion/illustration.
Plans
Plans allocate a monthly allowance of messages and data (messages in and out) to be used for inbound and outbound processing. Plans/allowances are allocated/refreshed on the first day of each month. The size of allowance granted depends on the number of users paid for by the subscription. If your user tier increases you'll be eligible to go up to the next Plan tier at the start of the following month.
Data limits scale linearly though all plan tiers, maintaining an average of 0.2 MB per message.
Plan
Users
Messages/month
Data/month
Max cost/month
Starter 
All Evaluations
250
75MB
n/a
Bronze1
1-10
4,000
0.5GB
$5
Bronze2
11-15
5,000
0.75GB
$37.5
Bronze3
16-25
6,000
1.0GB
$62.5
Bronze4
26-50
7,000
1.2GB
$125
Silver1
51-100
8,000
1.4GB
$250
Silver2
101-200
9,000
1.6GB
$400
Silver3
201-300
10,000
1.8GB
$500
Silver4
301-400
11,000
2.1GB
$550
Gold1
401-500
12,000
2.4GB
$600
Gold2
501-600
14,000
2.8GB
$650
Gold3
601-800
16,000
3.2GB
$750
Gold4
801-1000
18,000
3.6GB
$850
Platinum1
1001-1200
20,000
4.0GB
$950
Platinum2
1201-1400
22,000
4.25GB
$1,050
Platinum3
1401-1600
24,000
4.75GB
$1,150
Platinum4
1601-1800
26,000
5.00GB
$1,250
Platinum5
1801-2000
28,000
5.40GB
$1,350
Argon1
2001-2500
30,000
5.80GB
$1,600
Argon2
2501-3000
32,000
6.1GB
$1,850
Argon3
3001-3500
34,000
6.5GB
$2,100
Argon4
3501-4000
36,000
7.0GB
$2,350
Argon5
4001-4500
38,000
7.5GB
$2,600
Argon6
4501-5000
40,000
8.0GB
$2,850
Krypton1
5001-6000
45,000
8.6GB
$3,350
Krypton2
6001-7000
50,000
9.6GB
$3,850
Krypton3
7001-8000
55,000
10.5GB
$4,350
Krypton4
8001-9000
60,000
11.5GB
$4,850
Krypton5
9001-10000
65,000
12.5GB
$5,350
Krypton6
n/a
70,000
13.5GB
$5,850
Krypton7
n/a
75,000
14.5GB
$6,225
Xenon 1
n/a
100,000
20GB
$7,000
Xenon 2
n/a
150,000
30GB
$7,500
Xenon 3
n/a
200,000
40GB
$8,000
Xenon 4
n/a
250,000
50GB
$8,500
Xenon 5
n/a
300,000
60GB
$9,000
Xenon 6
n/a
350,000
70GB
$9,500
Radon 1
n/a
400,000
80GB
$10,000
Radon 2
n/a
600,000
120GB
$10,500
Radon 3
n/a
800,000
160GB
$11,000
Radon 4
n/a
1,000,000
200GB
$11,500
Unlimited
n/a
unlimited
unlimited
…
GB = gigabyte = 1000 MB, MB = megabyte = 1000 kB, kB = kilobyte = 1000 bytes. Prior to 1 July 2021 plans were presented using binary prefixes (e.g. 1 KiB = 1024 bytes).
- The "Starter" plan is limited in order to catch processing problems early. If you hit this limit during evaluation, email our support team referencing your host URL (e.g.
xxxx.atlassian.net) so we can bump up your capacity toward production levels. - Unlimited plan is for discussion only.
Customer migration
All customers will be allocated the plan according to the number of users that JEMHC is licensed for. Customers who already have a Plan Upgrade in place will be migrated to the new Plan of the same or greater capacity.
Plan allocation
JEMH Cloud assigns each Jira Host a monthly Plan. A Plan defines how much data and messages can be received and sent for that host. The host's Plan will be set based on the host's maximum number of users.
When JEMH Cloud processes (inbound) and sends an email (outbound), the host's usage will be increased adding 1 to the messages used and adding the email size to the data used. The email size includes attachments and the user images JEMH Cloud stores
When JEMH Cloud downloads an attachment from Jira, it counts towards data. Attachments may be downloaded to be sent in notifications and for attachment duplication detection
When JEMH Cloud uploads an attachment to Jira, it counts towards data. Attachments and images are uploaded from emails to the issues
Running Test Cases and all derived notifications count towards usage
A monthly plan limit is reached once the monthly messages OR data used is greater that what the Plan defines. Once the limit has been exceeded, JEMH Cloud will not process any more inbound emails. The usage will be reset on the 1st of every month.
Why do trials get allocated the small capacity Starter Plan?
New evaluations are put onto the limited capacity Starter evaluation plan to stop excessive erroneous email processing while you are configuring the app. Once normal email processing has been shown, contact our sales team to get a higher capacity plan. You are notified of usage once 80% (data or messages) is reached. See JEMHC > Licensing > System Notifications to change this threshold and who is notified.
Do Plans change?
Yes, plans are reviewed on a regular basis. Updates to Plans will be noted on the JEMHC blog.
Data Packs
If your company needs to process more messages or data than the monthly Plan allows, you can buy Data Packs that act as a reserve of messages and data that is used after the monthly Plan has been consumed. If you’re not yet at production levels, contact our support teamreferring your host URL (e.g.xxxx.atlassian.net).History and Expiry
Records of purchased Data Packs can be found in JEMHC > Licensing > Plans (scroll down). Data packs remain usable before one year from purchase, after which time they are dropped, causing unused messages and data to be be removed.
A Data Pack is consumed once all its messages OR data are consumed (zero messages OR zero data left). When a new month starts, all unconsumed Data Packs are available after the host consumes its standard monthly Plan allowance (messages or data).
Purchasing
Data Packs can be purchased directly through our online shop. Your Atlassian host URL (e.g. your.atlassian.net) is required so make sure you have that to hand. Once the purchase is completed, the data pack is automatically applied to your JEMH Cloud app.
Data Pack Size
Messages
Data
$ USD
Small
1500
125 MB
100
Medium
3000
250 MB
200
Large
6000
500 MB
400
Extra Large
12000
1.0 GB
800
XL Data 1.5GB
0
1.5 GB
600
XL Data 3GB
0
3.0 GB
1080
XL Data 6GB
0
6.0 GB
1944
XL Data 12GB
0
12.0 GB
3500
XL Data 24 GB
0
24.0 GB
6300
| Info |
|---|
Currently, the checkout process is Credit Card only via PayPal. Invoicing is also of course supported, for that please email our sales team and indicate what Data Pack Size you need and what your Atlassian host URL is. |
Plan upgrades
If message count or data volume is regularly exceeded, it is more cost effective to upgrade your plan. As the numbers of users remains the same, the Atlassian marketplace billing will also remain the same. What will be required is an out-of-band purchase for the upgrade. Subscription purchases are not applicable to plan upgrades - its expected that customers wanting this would be looking at an annual period. Plan upgrades are non-refundable and non-transferable. Customers are expected to remain at least at their initial tier for the period. If customer subscription levels drop below the one the upgrade was based on, customers will be asked to top up their plan upgrade accordingly (as upgrade pricing factors in existing tier subscription).
A Plan Upgrade doesn’t add capacity, it only increases the maximum per month. If usage (including Data packs) exceeds what the Plan Upgrade maximum is, a Data Pack would be required.
Regretfully, without exception all plan upgrades must be paid before allocation.
Plan Upgrades are a one year fixed term capacity upgrade.
Plan Upgrades cannot be purchased through Atlassian Marketplace which has no concept of volume-related billing at this time.
, priced in tiered plans (below). In cloud, a user is an active user in your instance (Jira Service Management customers don’t count as active users).
For the latest pricing details, please visit https://marketplace.atlassian.com/apps/4832/enterprise-mail-handler-for-jira-jemh?tab=pricing&hosting=cloud.
Plan capacity and usage
Capacity Plans grant customers a certain amount of messages and data every month. They are refreshed on the first day of each month, based on the active users in your subscription. Message count and data volume increases as you increase in plan size (reflecting all email your instance receives in and sends out).
What happens when you run out of capacity?
Processing of inbound mail and the generation of outbound notifications stop. No data is lost in this scenario - as soon as there is sufficient capacity available, processing will continue.
If plan capacity is exhausted, more can be acquired in two ways:
Purchasing a Data Pack, a one off capacity increase (Messages , Data or a combination of both)
Purchasing a Plan Upgrade (see Capacity Plans )
Quotes can be requested from sales@thepluginpeople.com or though our Support Portal, it is possible purchase Data Pack out of hours using a credit card through our Online Store.
| Info |
|---|
All additional capacity related purchases must be paid before allocation. |
How is plan usage calculated?
See How plan consumption is calculated.
When is plan usage reset
JEMH allocates capacity plans to customers based on their paid Atlassian subscription users on the 1st of every month. Plan Upgrades can occur at any time, however, are allocated on payment only.
Why do trials get allocated the small capacity Starter Plan?
New evaluations are put onto the limited capacity Starter evaluation plan to stop excessive erroneous email processing while you are configuring the app. Once normal email processing has been shown, contact our sales team to get a higher capacity plan. You are notified of usage once 80% (data or messages) is consumed. See JEMHC > Licensing > System Notifications to change this threshold and who is notified.
Do Plans change?
Yes, plans are reviewed on a regular basis. Updates to Plans will be communicated via the JEMHC blog.
Any changes to your plan are shown in the plan refresh notification sent each month. The plan transition types below explain what each type covers:
Install - New installations of the app will be shown as an install transition.
Manual - If you have contacted support and had a recent plan change, it will be shown as a manual transition.
Auto - If your active user count automatically moves you to a higher plan tier, this will be shown as an automatic transition.
Data Center to Cloud migration
We support Data Center customers with Dual Licensing (a free DC license),where over 1000 user subscriptions are purchased for a year term in advance.
Server to Cloud
JEMH for Jira Server is not paid through Atlassian Marketplace and is not part of the Dual Licensing path. As Server licenses are perpetual, they can of course continue to be used indefinitely for versions released in your maintenance window. Maintenance for Server can be renewed for a minimum 4 month term as needed. For more information, contact our sales team.
Academic & Community licensing
Subscription costs
JEMH Cloud follows Atlassian's cloud app licensing policy for Academic and Community pricing. In order to get a free community app license you need to:
Have a community Jira instance license already: https://www.atlassian.com/software/views/community-license-request
Request a community license through Atlassian https://www.atlassian.com/company/contact/purchasing-licensing
| Info |
|---|
Free use covers basic allocated capacity only. Additional capacity is available through Data Packs, see below for community discounts, when requesting a quote for Data Pack be sure to refer your App entitlement number. |
Atlassian partners
Free subscriptions are supported for Atlassian partners, however capacity limits apply based on subscription user level. See ‘Additional capacity costs'.
Quoting & purchasing
We do not issue quotes for subscription costs. Annual quoting is possible via Atlassian Marketplace with monthly subscription pricing is shown on the JEMHC Marketplace entry, see Per-user pricing below for pay as you go monthly subscription costs.
Why isn't unlimited usage part of the subscription fee?
While we would like to provide customers with unlimited usage capacity, it's not feasible in reality. Some customers need significantly higher capacity than others, and this increased capacity comes with costs. At present, we consider using plans as the fairest solution.
Some users want messages while others want data, or a mix. We try to balance plans so that there is something for everyone - sometimes this means the suggested plan is not suitable for you. In this case, most likely you'll need a Plan Upgrade. Plans are not intended to be a cash generator - they are a way of controlling excessive use by the few.
License types
All pricing shown here and on our Online Store are for commercially licensed instances.
Discounts
Discounts are only available for specific customer license types and for when they are made directly through our sales@ / support@ mailboxes. Purchases made directly through the online shop are not discounted, regardless of license type, no refund or credit will be offered.
The following customer license types are eligible for discounts when making direct purchases through sales@ / support@ mailboxes.
Academic
Community
Classroom
Open Source
Atlassian partners already get discounts through https://developer.atlassian.com/platform/marketplace/app-discount-programs/ that apply to subscription billing, we don’t usually have more.
We offer a flat rate of 50% for DataPacks and Plan Upgrades. Capacity allocations are only made on payment receipt.
Migrating from Server & Other License Type?
Once you have established your Jira cloud instance license type with Atlassian, it should fit into the model above, e.g. 'Community'.
Customer migration
All customers will be allocated the plan according to the number of users that JEMHC is licensed for. Customers who already have a Plan Upgrade in place will be migrated to the new Plan of the same or greater capacity.
Have you purchased an annual license?
Atlassian license response only indicate the active users in your instance (https://ecosystem.atlassian.net/browse/FRGE-815 ). We are happy to allocate the correct plan for the term of your annual license on request, just contact our support teamreferring your host URL (e.g. xxxx.atlassian.net) and EIN/SEN
Data Packs
If your site needs to process more messages or data than your standard monthly Plan allows, you can buy Data Packs that act as a reserve of messages and data. Data Pack capacity is used after the monthly allowance has been consumed. If you’re not yet at production levels, contact our support teamreferring your host URL (e.g. xxxx.atlassian.net). If plan limits are frequently reached, you may find it is more cost effective to upgrade your plan instead of buying Data Packs
History and Expiry
Records of purchased Data Packs can be found via JEMHC > Licensing > Plans. Data packs remain usable for one year from date of purchase, after which time they expire along with their unused message and data capacity.
A Data Pack is consumed once all its messages OR data are consumed (zero messages OR zero data left). When a new month starts, all unconsumed Data Packs are available after the host consumes its standard monthly Plan allowance (messages or data).
Purchasing
Data Packs can be purchased online (PayPal acct required) and automatically applied when:
Use the Online Shop
Refer your Atlassian host URL (e.g.
your.atlassian.net) during checkout
If you require a card-only checkout, this can be done by request through sales@thepluginpeople.com
Data Pack size | Messages | Data | Price (USD) |
|---|---|---|---|
Small | 1500 | 125 MB | 100 |
Medium | 3000 | 250 MB | 200 |
Large | 6000 | 500 MB | 400 |
Extra Large | 12000 | 1.0 GB | 800 |
XL Data 1.5GB | 0 | 1.5 GB | 600 |
XL Data 3GB | 0 | 3.0 GB | 1080 |
XL Data 6GB | 0 | 6.0 GB | 1944 |
XL Data 12GB | 0 | 12.0 GB | 3500 |
XL Data 24 GB | 0 | 24.0 GB | 6300 |
| Info |
|---|
Purchases can be done through quote/invoice. Payment methods are limited to wire transfer or credit card via PayPal clearing. For quotes/invoices, please email our sales team at sales@thepluginpeople.com and indicate what Data Pack Size you need and what your Atlassian host URL is, as well as your business's physical address and EU VAT# if applicable. |
Plan upgrades
Upgrading your assigned plan to a higher tier is a cost effective way to increase your maximum message and data allowance. It is recommended over Data Packs in cases where monthly limits are being frequently reached. The Atlassian app pricing model doesn’t support capacity related billing so currently upgrades must be purchased directly from us (The Plugin People), separately from subscription billing. To upgrade, contact our sales team referencing your Atlassian host URL
,and which plan you want to
upgrade to.How its calculated
Plan Upgrades are for a one year fixed term and are calculated as 10 times the difference in per-user pricing between "one user into the new tier" and the Average of the old tier, thereby providing the same level of discount as Atlassian annual subscriptions (12 months for the price of 10).
Plan Upgrade examples
Upgrade example
Working out
Bronze 1 to Bronze4
Bronze4 starts at 26 users, 26 users comes in the 1-100 user range, so that’s (26*2.50) == $65 per month
The average user level within Bronze1 is 5 users, so that's (5*2.50) == $12.5
Upgrade cost is then 10 * (65 - 12.5) = $525 per year
Bronze1 to Silver1
Silver1 starts at 51 users, the first 51 are at $2.50 (from the 1-100 tier), so Silver1 requires (51*2.5) == $127.50 per month
The average user level within Bronze1 is 5 users, so that's (5*2.50) == $12.5
Upgrade cost is then 10 * (127.50 - 12.5) == $1150 per year
Silver2 to Gold4
Gold4 starts at 801 users, the first 100 are at $2.50 (from the 1-100 tier), the next 150 are at $1.50 (from the 101-250 tier), the next 551 are at $0.50 (from the 251-1000 tier), so that’s (250 + 225 + 275.5) == $750.5 per month
The average user level within Silver2 is 150 users, so the first 100 are at $2.50 (from the 1-100 tier), the next 50 are at $1.50 (from the 101-250 tier) so that's (250 + 75) == $325
Upgrade cost is then 10 * ($750.5 - 325) == $4250 per year
Argon1 to Krypton1
Krypton1 starts at 5001 users, the first 100 are at $2.50 (from the 1-100 tier), the next 150 are at $1.50 (from the 101-250 tier), the next 750 are at $0.50 (from the 251-1000 tier), the next 4000 are at $0.50 (from the 1001-to 5000 tier), then 1 final user at $0.5, so that's (250 + 225 + 375 + 2000 + 0.5) == $2850.5 per month.
The average user level within Argon1 is 2250 users, so the first 100 are at $2.50 (from the 1-100 tier), the next 150 at $1.5 (from the 101-250 tier), the next 750 at $0.50 (from the 251-1000 tier), the next 1250 users are at $0.50 (from the 1001-to 5000 tier), so that’s (250 + 225 + 375 + 625) == $1475
Upgrade cost is then 10 * (2850.5 - 1475) == $13,755 per year
Upgrading whilst a Plan Upgrade is active
If you need to upgrade whilst one is active, remaining fully unused months can be credited against a new Plan Upgrade from your current user-based Plan to the desired plan.
Example
If you have 10 Users, the user-based plan allocation will be Bronze1. A plan upgrade from Bronze1 to Bronze4 (see examples above) will be $525 for a 12 month term. 5 months and a day later, a Plan Upgrade to Silver 1 is required. This will be calculated as Bronze 1 > Silver upgrade ($1150) minus remaining six full months of the existing Bronze 1 > Bronze 4 upgrade (6 * $525/12), so that's $1150 - $262.50 == $887.50 due.
What happens if your user count drops below the pre Plan Upgrade level
If your user level causes your (pre-upgrade) allocated Plan to drop below the level before Plan Upgrade, your upgrade term will be reduced in monthly increments to cover.
Example scenario
You plan was Bronze 4, then a Plan Upgrade was purchased to Silver 4, after which, at some point, your users cause the pre-upgrade mapped Plan to drop below Bronze.
Evaluation Period
Please don't try to extend your evaluation period beyond the standard duration. If you uninstall and reinstall, cancel an Active license and try to start a new evaluation, it may appear that you can start an evaluation but it will not work.
The Pricing FAQ tab contains a section 'Can I extend my free trial' of the JEMHC Add-on listing:
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
The Initial Evaluation Period should not be more than 60 days in any scenario. When evaluations complete, you can either subscribe to the JEMHC service, or cancel. When evaluations expire no access to JEMHC features or UI will be possible - all mail retrieval will stop, and no outbound notifications will be sent. If a subscription doesn't start after 30 days, all configuration and data will be purged automatically (if defined, your contact email address will be notified of this action).
Once the initial Evaluation Period has been passed, only Active licenses will be supported, the re-installation of further evaluation licenses will not be valid, ever! Repeat evaluations would be possible if the service is cancelled and left idle for 30 days (to trigger host purging).
Consequences of Cancelling/ Uninstalling : License Cycling
If you cancel an active subscription (that actually doesn't result in a payment to us until the end of the month) you will need to become active once more in order to use JEMHC. Regardless of what Marketplace indicates as a valid Evaluation license JEMHC sees this as abuse and blocks it. As there is no way to purchase cloud apps without first trialling (see https://ecosystem.atlassian.net/browse/AMKT-22742), you will need to contact Atlassian support. Apparently they will not be able to ‘progress’ an order until you actually start a trial, so you will need to contact us after raising an issue with Atlassian to enable a time-limited evaluation. This will give you and Atlassian time to complete the purchase and get your status Active (you need to push back if you get answers from support along lines of 'active after evaluation’). If a license is not found to be Active after a short time, app access will be voided.
Bugs with Annual terms
We've had several cases where annual purchases don't actually go through on Atlassian licensing system, so as a 3rd party app we are simply informed you have no license. If you have purchased a year term but seem to be locked out of the app, contact Atlassian support as we can’t solve this directly.
Expired Evaluations
Any evaluation license that exists for more than 61 days becomes expired. If a customer has not provided valid payment details at this point, no further processing will occur until the license turns active. Restarting an evaluation will not work and is not advised (see License Cycling above).
Voided licenses
In some exceptionally rare situations, it may be required to void user licenses to stop automated installations of the add-on or prevent abuse. If this happens:
The app will not function regardless of license state (installing a new evaluation or going Active won't change voided status)
Clearing the voided status is possible only by contacting us (please refer your Jira host name when doing so)
upgrade to.
| Info |
|---|
|
Calculating Plan Upgrade costs
The Capacity Plans page contains a full list of tiers, and the cost calculations for Plan Upgrades.
Upgrading while a Plan Upgrade is active
If you need to upgrade while an upgrade is already active, the remaining fully unused months can be credited against a new Plan Upgrade from your current user-based plan to the desired plan.
Example
If you have 10 Users, the user-based plan allocation will be Bronze1. A plan upgrade from Bronze1 to Bronze4 (see examples above) will be $525 for a 12 month term. 5 months and a day later, a Plan Upgrade to Silver 1 is required. This will be calculated as Bronze 1 > Silver upgrade ($1150) minus remaining six full months of the existing Bronze 1 > Bronze 4 upgrade (6 * $525/12), so that's $1150 - $262.50 == $887.50 due.
What happens if your user count drops below the pre Plan Upgrade level
If your user level causes your (pre-upgrade) allocated Plan to drop below the level before Plan Upgrade, your upgrade term will be reduced in monthly increments to cover.
Example scenario
Your plan was Bronze 4, then a Plan Upgrade to Silver 4 was purchased. Then, at some point your user count causes the pre-upgrade mapped Plan to drop below Bronze.
What happens if you cancel the JEMHC subscription
Plan upgrades are non-refundable.
Evaluation Period
The evaluation period is fixed by Atlassian. Please refrain from attempting to extend your evaluation period by cycling licenses (uninstalling and reinstalling and/or canceling an Active license and trying to start a new evaluation) - it may seem possible to start an evaluation, but it will not work.
The Pricing FAQ tab contains a section 'Can I extend my free trial' of the JEMHC Add-on listing:
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
The Initial Evaluation Period should not be more than 62 days in any scenario. When evaluations complete, you can either subscribe to the JEMHC service, or cancel. When evaluations expire no access to JEMHC features or UI will be possible - all mail retrieval will stop, and no outbound notifications will be sent. If a subscription doesn't start after 30 days, all configuration and data will be purged automatically (if defined, your contact email address will be notified of this action).
Once the Initial Evaluation Period has passed, only Active licenses will be supported. The re-installation of further evaluation licenses will not be valid. Repeat evaluations would be possible if the service is cancelled and left idle for 30 days (to trigger host purging).
Evaluation period extensions are not usually granted. If customers exceed 60 days for evaluation, we suggest transitioning to a monthly subscription with no significant annual cost. To continue into the 3rd month, take no action; payment will occur at month-end. Otherwise, cancel and receive an Atlassian refund.
Consequences of Cancellation / non-payment
To use JEMHC after a canceled active license or failed payment, you will need to switch to an active license immediately. You can initiate this process through support.atlassian.com since there is no option for 'buy now' for cloud apps.
Consequences of Cancelling/ Uninstalling : License Cycling
If you cancel an active subscription (that actually doesn't result in a payment to us until the end of the month) you will need to become active once more in order to use JEMHC. Regardless of what Marketplace indicates as a valid Evaluation license JEMHC sees this as abuse and blocks it (https://ecosystem.atlassian.net/browse/AMKT-12613 ). As there is no way to purchase cloud apps without first trialing (see https://ecosystem.atlassian.net/browse/AMKT-22742), you will need to contact Atlassian support. Apparently they will not be able to ‘progress’ an order until you actually start a trial, so you will need to contact us after raising an issue with Atlassian to enable a time-limited evaluation. This will give you and Atlassian time to complete the purchase and get your status Active (you need to push back if you get answers from support along lines of 'active after evaluation’). If a license is not found to be Active after a short time, app access will be voided.
Bugs with Annual terms
Annual purchases may not register immediately in Atlassian's system, leading to incorrect license status. If you've bought a yearly subscription but can't access the application, contact Atlassian support for assistance.
Expired evaluations
Evaluation licenses expire after 62 days. Any cancellation of an evaluation cannot be restarted after 7 days from the first evaluation starting (cancelling does not allow a new evaluation period).
If a customer has not provided valid payment details at this point, no further processing will occur until the license turns active. Restarting an evaluation will not work and is not advised (see License Cycling above).
Voided licenses
In some exceptionally rare situations, it may be required to void user licenses to stop automated installations of the app or prevent abuse. If this happens:
The app will not function regardless of license state (installing a new evaluation or going Active won't change voided status)
Clearing the voided status is possible only by contacting us (please refer your Jira host name when doing so)
Voided hosts will be immediately inactive, and after 30 days will have all configuration and other retained data purged. Once purged, hosts are free to install an initial evaluation again.
Testing
Extending initial evals
Evals are limited in duration (see Evaluation Period above) extending them is typically not possible, ensure billing details are present on the billing user for the instance to avoid impact at the point of billing.
The Plugin People are not responsible for the issuance of any cloud licenses. If you are starting a migration and need a specific fixed term for that to occur, you will need to go through http://support.atlassian.com , and gain authorization from us through our Support Portal.
Longer term test instance
There are only a few paths:
a) Create a new test eval instance and setup from scratch, leaving the instance to expire out once the license lapses
b) License a second small scale 10 user instance to rretain configuration
c) Use a sandbox instance (requires Premium/Enterprise platform license), see https://support.atlassian.com/organization-administration/docs/what-are-sandboxes/
Privacy
See our Privacy Policy and related Cookie Policy.
EULA
This software is licensed under the provisions of the Standard EULA from the Atlassian Marketplace Terms of Use as a Marketplace Product.
The "Standard EULA" is reproduced here for convenience. In this case, the "Publisher" is The Plugin People Ltd:
(i) The Publisher is the licensor of the Marketplace Product and Atlassian is not a party to the Publisher EULA or this Standard EULA, as applicable.
(ii) If the Marketplace Product does not include a Publisher EULA that specifies Marketplace Product license rights, Publisher grants you a limited, worldwide, non-exclusive, non-transferable and non-sublicensable license to download and use the Marketplace Product only on hardware systems owned, leased or controlled by you.
(iii) Licenses granted by Publisher are granted subject to the condition that you must ensure the maximum number of Authorized Users that are able to access and use the Marketplace Product concurrently is equal to the number of User Licenses for which the necessary fees have been paid to Atlassian and/or its authorized partners (each, an "Atlassian Expert"). You may purchase additional User Licenses at any time on payment of the appropriate fees to Atlassian or an Atlassian Expert. "User License" means a license granted under this EULA to you to permit an Authorized User to use the Marketplace Product. The number of User Licenses granted to you is dependent on the fees paid by you. "Authorized User" means a person who accesses and uses a Marketplace Product under the EULA and for which the necessary fees have been paid to Atlassian and/or an Atlassian Expert.
(iv) Any information that Publisher collects from you or your device will be subject to any Publisher EULA, privacy notice, or similar terms that the Publisher provides to you, and will not be subject to the Atlassian Privacy Policy (unless Atlassian is the Publisher).
(v) You may not modify, reverse engineer, decompile or disassemble the Marketplace Product in whole or in part, or create any derivative works from or sublicense any rights in the Marketplace Product, unless otherwise expressly authorized in writing by Publisher.
(vi) The Marketplace Product is protected by copyright and other intellectual property laws and treaties. Unless otherwise expressly stated in the Publisher EULA, Publisher or its licensors own all title, copyright and other intellectual property rights in the Marketplace Product, and the Marketplace Product is licensed to you directly by the Publisher, not sold.
Additional Terms
This product is covered by our Cloud Software Product EULA that now includes the Data Processing Addendum (DPA)for this app. By subscribing to the app, these terms are automatically accepted.