Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

JEMH License expired

TasneemB March 24, 2017



Please advise what would happen if JEMH license expired? Will mails still be processed as per normal? REason I ask is my JEMH license has expired and SOME mails are being processed, whereas I am getting forwarding exceptions on others with following error. It also gives hints that the 'Default Reporter' value does not have create issue permission


Could this be a result of the expired license?


The email did not result in a creation/comment/update.  Check user creation config, email addresse mappings, project mappings and project level security.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Andy Brook
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 24, 2017

About expiry:

  1. If you have a commercial license, you have a perpetual right to use any version of JEMH released within your maintenance window.  If you upgrade your JEMH after its expired, then most of the JEMH UI will be disabled and JEMH will not process inbound email, or generate outbound notifications, as you are not licensed.  You'll need to talk to to get a maintenance renewal, which is only available up to 12 months since it previously expired, beyond which time a new purchase will be required.
  2. If you have an eval, its valid until it expires (usually 30days) then you'll need to talk to for an extension


The message you show is from the JEMH application, in the audit record.  That you can see this means that JEMH is operational.  The error is pretty specific in the outcome, no issue was created/updated.  The cause can be many things, perhaps mandatory custom field, a validator or a condition, even something as an unexpected 'default' issue type (eg Epic) that then requires a particular field eg "Epic Name".

> It also gives hints that the 'Default Reporter' value does not have create issue permission

Well, that does seem rather specific, and would explain the error, perhaps you need to fix that?

AUG Leaders

Atlassian Community Events