How to Raise a Good JEMH Bug

No, email isn't best, really

Much as I like to hear about people using JEMH and want to help with issues, my inbox is not the place for timely support assistance (I may miss it or forget to respond due to volume), to help me help you, please consider the following methods instead:

Quick questions

Forums

Feel free to use the NEW and SHINY Confluence Questions for quick Q&A type matters.

Project JIRA

All issues and support requests are managed through the JEMH Project (free reg)

Issue Security

As email content is usually required to facilitate problem diagnosis, when creating the issue, please ensure issue security is enabled if you have privacy concerns.

Current releases of JEMH have the following Nav toolbar:

Good Bug(tm)

In order of usefulness...

  1. JIRA version

  2. JEMH version

  3. Database type/version

  4. JEMH Profile export

  5. JEMH TestCase email that can be used to reproduce the problem (JEMH Audit history can convert an audit event into a Test Case)

BadBugs(tm)

The number of times I see reports like "JEMH doesn't work" and that's it. Such reports are time wasters and likely to be marked invalid on sight.