Page Comparison

How pricing

works

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.

Discounts

As per https://developer.atlassian.com/platform/marketplace/app-discount-programs :

Data Center to Cloud

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 supports Academic and Community pricing models for basic subscription costs, see https://developer.atlassian.com/platform/marketplace/cloud-app-licensing/ for more. In line with the basic subscription discounts, JEMHC top-up DataPacks 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

The Plugin People do not quote for cloud subscriptions;

• per-user pricing is listed on the JEMHC Marketplace entry

• all quoting is all handled through Atlassian Marketplace, you can generate a quote here.

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 msgs of 20MB = 2000MB of data used)

Free notifications that are not billed /counted involve low data/impact services like web-driven SMS and IM (Slack) 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 (for example, at the end of NOV 2018 ~1.5% of hosts exceeded Plan capacities).

License Types

All pricing here (and the e-junkie shop) are for commercially licensed instances. Discounts can only be handled through sales@thepluginpeople.com. Purchases are final and non-refundable. The following discounts apply for Plan Upgrades and DataPacks:

• see https://developer.atlassian.com/platform/marketplace/app-discount-programs/ for comparison of subscription cost discounts

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 9 OCT 2020

Users

Monthly rate

Max (monthly)

Max (annual, 10months)

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.15

$1450

$14500

5001-10,000 users

$1450 + (users -5000) * $0.10

$1950

$19500

Further pricing Examples

The two tables below show the maximum monthly cost for a given Plan.

Plans for <2000 Users

Bronze1

Bronze2

Bronze3

Bronze4

Silver1

Silver2

Silver3

Silver4

Gold1

Gold2

Gold3

Gold4

Platinum1

Platinum2

Platinum3

Platinum4

Platinum5

$5

$37.5

$62.5

$125

$250

$400

$500

$550

$600

$650

$750

$850

$880

$910.50

$940

$970

$1000

Plans for >2000 Users

Argon1

Argon2

Argon3

Argon4

Argon5

Argon6

Krypton1

Krypton2

Krypton3

Krypton4

Krypton5

$1075

$1150

$1225

$1300

$1375

$1450

$1550

$1650

$1750

$1850

$1950

Read more about per-user pricing:

• https://www.atlassian.com/licensing/cloud/future-pricing

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.

JEMHC Plan Allocations

Based on the annual user tier structure, all plan points above are met or exceeded in terms of capacity below (effective 9 OCT 2020):

Plan

Users

Messages

Data

Starter*

All Evaluations

250

75MB

Bronze1

1-10

3000

250MB

Bronze2

11-15

4000

350MB

Bronze3

16-25

5000

450MB

Bronze4

26-50

6000

512MB

Silver1

51-100

7000

576MB

Silver2

101-200

8000

640MB

Silver3

201-300

9000

768MB

Silver4

301-400

10000

896MB

Gold1

401-500

11000

1GB

Gold2

501-600

12000

1.13GB

Gold3

601-800

13000

1.25GB

Gold4

801-1000

14000

1.38GB

Platinum1

1001-1200

15000

1.5GB

Platinum2

1201-1400

16000

1.63GB

Platinum3

1401-1600

17000

1.88GB

Platinum4

1601-1800

18000

2.13GB

Platinum5

1801-2000

19000

2.38GB

Argon1

2001-2500

20000

2.75GB

Argon2

2501-3000

22000

3GB

Argon3

3001-3500

24000

3.25GB

Argon4

3501-4000

26000

3.5GB

Argon5

4001-4500

28000

3.75GB

Argon6

4501-5000

30000

4GB

Krypton1

5001-6000

31000

5GB

Krypton2

6001-7000

32000

5.5GB

Krypton3

7001-8000

33000

6GB

Krypton4

8001-9000

34000

6.5GB

Krypton5

9001-10000

35000

7GB

• The "Starter" plan is deliberately limited, to catch mail loop and processing problems early.  If whilst during evaluation, you hit this limit, reach out to jemhc-support@thepluginpeople.com referring your host (xxxx.atlassian.net) so we can bump up your capacity toward production levels.

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 sends a HipChat notification (outbound), the host's usage will be increased adding the notification size to the used data. Please note that PPL decided not to increase the used messages for HipChat notifications

• 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 new customers initially get allocated the very limited capacity Starter Plan?

New evaluations are put onto the limited capacity Starter evaluation plan to stop (all too common) runaway email processing which the user probably didn't want in any case.  Once normal email processing has been shown, new users can be bumped up onto higher plans as needed, just contact sales@thepluginpeople.com.  You would be informed of usage once 80% (data or messages) is reached.  See JEMHC > Licensing > System Notifications to change the limit, or who should be notified.

Do Plans change?

From time to time, Plans are modified.  Updates to Plans will be noted on the JEMHC blog.

Jira Cloud storage limits

Storage varies depending on your Jira Product plan (see Atlassian Cloud storage policy  for details).  If you need more, or want to host your data yourself, JEMHC provides an external cloud storage feature that allows uploading content to external storage systems (e.g. AmazonS3, Dropbox, Google Drive).  This uploaded content data still travels through JEMHC servers, and therefore still consumes data from your monthly plan allowance.  Future releases will allow JEMHC to make use of this in various ways, e.g. for storage of email attachments and even further down the path, for storing longer term archives of auditing email content.

Data Packs

History and Expiry

Records of purchased Data Packs can be found in JEMHC > Licensing > Plans (scroll down).   Data packs are valid for 1 year from purchase and will expire after one year from purchase 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 are purchased directly through our online shop. Once the purchase is completed, the data pack is automatically applied to your JEMH Cloud account.

Buy Now

JEMHC Online Shop

Place an Order

sales@thepluginpeople.com

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

 When selecting the Data Pack size, the 'domain' of your instance is needed (e.g.  yourco.atlassian.net) , to enable automated lookup of your instance and application of the pack.

 Currently, the checkout process is Credit Card only via PayPal.  Invoicing is also of course supported, for that please mail sales@thepluginpeople.com and indicate what Data Pack Size you need and what your domain is.

Plan Upgrades

If message count or data volume is regularly exceeded, it would be more cost effective to upgrade plans.  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).

NOTE:

• A Plan Upgrade does not add capacity, it only increases the maximums per month. It's possible that usage (including Data packs) may exceed what the Plan Upgrade maximum is, so will still require a Data Pack to be in credit.

• Regretfully, without exception, all plan upgrades must be paid before allocation.

• Plan Upgrades are a one year fixed term capacity upgrade.  If you exceed an upgraded Plan, you may still need a DataPack.

• Plan Upgrades cannot be purchased through Atlassian Marketplace which has no concept of volume-related billing at this time.  

• Purchasing plan upgrades can only be done via invoice, contact sales@thepluginpeople.com, be sure to refer 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 pcm

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 pcm

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 pcm

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.15 (from the 1001-to 5000 tier), then 1 final user at $0.1, so that's (250 + 225 + 375 + 600 + 0.1) == $1450.1 pcm

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.15 (from the 1001-to 5000 tier), so that’s (250 + 225 + 375 + 187.5) == $1037.5

Upgrade cost is then 10 * (1450.1 - 1037.5) == $4126 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 12month term.  5 months and a day later, a Plan Upgrade to Silver1 is required.  This will be calculated as Bronze1>Silver upgrade ($1150) minus remaining six full months of the existing Bronze1>Bronze4 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 Bronze4, then a Plan Upgrade was purchased to Silver4, after which, at some point, your users cause the pre-upgrade mapped Plan to drop below Bronze.

Evaluation Period

Short story

Please don't try to extend your eval period, it will end badly, the clock starts on the first evaluation, and keeps running, regardless of usage or license status.  If you uninstall and reinstall, cancel an Active license and try to start a new eval, it may appear that you can start an eval but JEMHC will block such actions (AMKT-12613).

Longer story

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).

License Cycling

If you cancel an ACTIVE , 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.

How is plan usage calculated?

See How plan consumption is calculated.

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:

1. Have a community Jira instance license already: https://www.atlassian.com/software/views/community-license-request

2. Request a community license through Atlassian https://www.atlassian.com/company/contact/purchasing-licensing

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:

1. Use the Online Shop

2. 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

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.

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 active once more in order to use JEMHC, regardless . Regardless of what Marketplace indicates as a valid Evaluation license JEMHC sees this as abuse and blocks it.  If you talk to Atlassian support about this please quote the following JST-162752 and refer the logged bug on the topic: AMKT-12613.

Can't buy it now...

There is currently no way to 'buy it now' for cloud apps 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).  In order to go active, we can on request enable your evaluation in JEMHC for a strictly limited timeframe in order for you to then progress the purchase.  Such re-evals are monitored and if they do not go active within a 48hr period, will be voided to an unlicensed state, 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 Atlassians licensing system, so as a 3rd party app, are informed you have no license.  If you have purchased a year term, but seem to be locked out of the app, then contact Atlassian support in the first instance, as there will be nothing we can directly do.

Expired Evaluations

Atlassian has changed how cloud add-ons are initially licensed.  If the Atlassian billing system is offline, cloud add-ons are initially reported as Active. Some time later when the billing system comes back on line, a background job runs over all affected hosts and sets their license status to Evaluation.  Currently this Active > Evaluation transition puts users license status into an Expired Evaluation (see above), locking out the add-on.  We will be fixing this so that affected users don't get blocked, subject to the transition happening quite soon after installation.

• For background : https://ecosystem.atlassian.net/browse/UPM-5541

Voided licenses

In some 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 add-on or in rare situations, prevent abuse (see the recent  blog entry quoting a recently sent email advising some users of this)app or prevent abuse.  If this happens:

• it wont be possible to use JEMHC, 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 jemhc-support@thepluginpeople.com us (please refer your Jira host name when doing so)

• Voided hosts will be immediately inactive, and after 30days will 30 days will have all configuration and other retained data purged.  Once purged, hosts are free to install an initial evaluation again.

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.