Versions Compared

Old Version 12

changes.mady.by.user Mike Harrison

Saved on

compared with

New Version Current

changes.mady.by.user Mike Harrison

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel
3
4
Dont Panic! We are here to help.
Tip
title
Info

Want to get help quickly?

Go to our support portal and create an account

Tip

This page will show you how to get in contact with us and get timely support.  It will also guide you on how to provide required information up front that will lead to a faster resolution of your issue!

Support Service

Support is provided, at least 8 hours a day 09:00 - 17:00 (UTC), 5 days a week, see the Support SLA.

General Support

We use JIRA Cloud for tracking all product related problems and support issues.  You can sign up for free to our issue tracker at 

Support SLA

See our Support SLA for details on when and how we provide support for our customers.

Support Channels

Email

Technical Support

Email users may also send support requests to support@thepluginpeople.com - this will create issues by email through our Enterprise Mail Handler for Jira Cloud app.

Sales Support

For sales related queries email can be sent to sales@thepluginpeople.com.

Jira

We are phasing out access to support issues via standard Jira issue view in favour of using the Customer Portal. Going forwards, support will only be available through the portal.

Pre-existing Atlassian ID Users with historic interactive access

Historic users have site access (but not app access to use Software directly) and will be redirected to the support Portal on access to our default site.

 to gain interactive use of our support system.Not sure where to raise an issue?  Use the SUPPORT Project - 

Confluence access is available by going to:

browse/SUPPORT.

Product Specific Projects

There are many specific JIRA Projects for each Product.  Some of them are listed below.  Don't see the project you are looking for?  Have a look at the full project directory.

JEMH : Enterprise Mail Handler for JIRA - 

New Atlassian ID users

New visitors will not be given site access, but, being unregistered will be able to access our Confluence anonymously. Such users must register for a separate Portal account to log support cases.

browse/JEMHEMQ : Enterprise Mail Queue for JIRA - 

Confluence access is available by going to:

browse/EMQ
  • SU for JIRA - https://thepluginpeople.atlassian.net/browse/JSU
  • SU for Confluence - https://thepluginpeople.atlassian.net/browse/CONFSU

    • Raising Issues by Email

    Email users may also send support requests to support@thepluginpeople.com , this will create issues by email through our brilliant JEMH Cloud product.

    Telephone

    Support by voice is not a primary support channel as the information usually required can't be easily expressed this way.  Please use the JIRA route initially!  For absolute "It's dead Jim" emergencies, see the Plugin People Vendor Profile on Marketplace, likely the outcome will still be to please log an issue!

    Tweet us!

    If you want to, tweet us @thepluginpeople if you can ask the question we'll try and respond, but you may be asked to please log an issue!

    When Logging an Issue

    Note

    Unexpected outcomes for reuse of email address from a removed account

    We found a bug in the Portal signup (seemingly closed https://jira.atlassian.com/browse/JSDCLOUD-6043), that prevents a previously registered email from being re-used (regardless of whether that account exists any longer) for a Portal account. In this case, registration appears to complete, but fails silently, no portal account is created and no ‘validation’ email ever arrives. Atlassian is aware, we have an open support case to resolve.

    If this affects your access, we recommend creating a portal account with an alternate email, or using a sub-address in your main email (e.g.: user@domain.com becomes user+ppl@domain.com) that will still ‘deliver’ to the main address. If you use the sub-address path, note that:

    Creating a Portal Account

    1. Sign up here

    2. Check your mail for a mail from jira@thepluginpeople.atlassian.net with subject Finish signing up to The Plugin People

    3. Click Sign-Up and set your display name and password

    Accessing the portal

    The portal is here

    Existing Atlassian ID Users

    Existing Atlassian ID users are being gradually removed from the site, historic issues remain.

    Historic support case migration

    Historic support issues can be migrated to an existing portal account with the same registered email address on request.

    Confluence access

    Public read only access remains for all variants users (anonymous, portal user or Atlassian ID).

    Telephone and Remote Desktop Sharing

    Support by Telephone or Remote Desktop Sharing are not our primary support channels.  We are usually able to resolve most support requests quickly through our Jira, so this is the recommended way to contact us.  For absolute emergencies, see the Plugin People Homepage on Atlassian Marketplace for details.  It is likely that you will still be required to log an issue through the Portal in order to allow us to track progress.  If we deem sufficient progress cannot be made through Jira correspondence alone, we may opt for a more hands on support method although it is not a first option.

    Requested information when logging a Support Request

    Summary

    Make the summary something that concisely describes your problem, "Its broken" or "It doesn't work" is non-specific and doesn't aid understanding!

    Description

    Make the description more detailed that the summary, provide a walk through of:

    • What is the result you want to get

    • What results are you getting now

    • What have you tried to fix it?

    Required Data

    The following are globally required values, please remember to set key information on the issue when logging a support case:

    • Atlassian application and version, e.g.

    JIRA

    • Jira 6.2.7

    • Database, if you have a start up problem (e.g.

    Mysql

    • PostgreSQL,

    Postgres

    • MySQL)

    • Plugin People Product name (e.g. JEMH, SU, EMQ)

    • Plugin People Product version (e.g. 1.2)

    Time/

    IssueKeyCommon logs required are:

    Issue Key

    If logs are provided, please identify the time at which the problem was observed, and the issue involved.

    JEMH Specific Support Information

    Logs

    Logs are great, they have much detail that can be useful, please DO NOT paste log content into descriptions, its hard to read, please DO attach them as text, if there are <20 lines that are important, sure paste them in {noformat} .... {noformat} markup blocks

    Log Filename

    Location

    Notes

    atlassian-jira.log

     (located in

    JIRA_HOME_DIRECTORY/log

    ), this is very useful, and provides some related background

    Can give an insight into potential problems that Jira is experiencing.

    atlassian-jira-incoming-mail.log

    (located in

    JIRA_HOME_DIRECTORY/log

    , enabled via JIRA

    Provides information about emails retrieved by Jira. Enabled via Jira System Admin > Troubleshooting and Support > Logging & Profiling >  Mail > Incoming Mail), it needs to be ENABLED

    and

    with DEBUGGING enabled too.

    jemh.log (previously emh.log

    (located in

    )

    JIRA_HOME

    /log), See Installation, Setup and Logging for configuration steps, this is a physical change to the log4j.properties file, and requires a JIRA restart, so may require scheduling to apply.  The benefit is that it puts all JEMH logging in one place, with no logging distractions from anything else in the systemWhen attaching logs,  please DO identify a Time

    _DIRECTORY/log

    See Enabling JEMH logging for steps on enabling

    (tick) DO identify and let us know specific times to look at in the log file, and if applicable, Issue key that identifies the time you observed the problem.  If you are not clear on the time, reproduce the problem by creating a JEMH Test Case from JEMH Audit History email content (there is an option for each audit history row).

    Problems relating to email processing

    DO attach

    (error) DO NOT paste large log content into Jira issue descriptions or comments.  Attach as a file instead!

    Emails

    (tick) DO attach plain text emails via JEMH Audit History exports of emails that you can confirm have caused a problem, and ideally, you can still confirm cause a problem by converting them into a JEMH Test Case and running it against your Profile.

    (error) DO NOT attach .msg format files where possible.  They are a binary proprietary format that cannot be used as easily as a plain text email.

    (tick) DO attach a complete example, as exported from the JEMH Auditing page (if you don't have this enabled, do so, and repeat the trigger to collect it).  Proving fake email content that you believe expresses the problem may work in some cases but may also waste a lot of time

    , with to/fro clarification

    , delaying resolution of your

    problem

     problem!

    DO attach

    (error) DO NOT attach drag and drop email content from Outlook, they are a proprietary binary format, can't be used and will be deleted if uploaded.

    (tick) DO attach your current Profile XML, exported from the JEMH Profile list page - in doing so validate that it is the same Profile that is associated with your inbound mail server.

  • DO NOT attach drag and drop email content from Outlook, they are a proprietary binary format, can't be used and will be deleted if uploaded.



    • Problems relating to issue creation / permissions

    If all your users are full

    JIRA

    Jira interactive users, validate their access to the expected projects.  

    For non-interactive

    JIRA

    Jira account users, validate the access (perhaps by JEMH allocated groups) are sufficient for the expected projects.

    For email only users without any kind of

    JIRA

    Jira account, validate the access allocated to the Profile default reporter for the expected projects.

    (info) Testing permissions is really quick and easy, just create a JEMH Test Case, from: the user in question to:  your inbound mailbox and run it!

    Licensing Issue

    DO

    (tick) DO give TEXT copies of your

    ServerID

    Server ID and Organisation name from the

    JIRA

    Jira license screen, screenshots mean rekeying, possibly introducing typos, lets get it right first time!

    Check the common problems page for existing resolutions

    Some common problems have cropped up over time, see the Common Problems Page for resolutions.