We always appreciate feedback. This article is meant to answer how to best submit bug reports, report crashes, and how to request new features.
RELATED LINKS:
JMP 17 RELEASE DATES
EARLY ADOPTER FAQ
OPEN ALLCLOSE ALL
How to report a problem?
A problem can be something that is broken or doesn’t work quite right (a bug), a UI issue, gaps in documentation, numerical errors, or missing options that you really need for an existing feature.
- Production version – email Tech Support at support@jmp.com.
- EA version – use jmpbeta@jmp.com. Make sure to mention which EA you are using. Or, use the option in the JMP EA menu to submit a bug report.
- Daily build – use jmpbeta@jmp.com. Make sure to mention which date of the build you are using. There’s a nice JSL command called build information().
How can I request a new feature or functionality?
Features are missing functionality, anything in the “it would be nice if…” category. An Epic is an entirely new feature set, new area for JMP or a brand new way of thinking about something in JMP. For example, “functional data analysis” was a big new feature that is an Epic, composed of many smaller pieces. Ultimately an epic changes the story in a big way or small way about what JMP can do.
For features and epics, please use the Internal Wish List so that product management is able to capture and manage all internal product feature requests. It is helpful to know the answers to the following questions:
- What inspired this Wish List Request?
- Please describe the new or improved feature or solution you would like to see.
- What would the value be to you and/or other users if this new feature is provided?
- Is this an external customer request?
- Is there a competitive software package that has this feature or solution that we should be aware of?
- Will this impact a renewal, expansion, or adoption at a customer, and does this put an account at risk if we do not address this?
Please DO NOT contact developers about adding new features or functionality.
How to get an early (beta) version of JMP?
How to report a crash?
- A crash is just another ‘thing that is wrong with JMP’ that we need to fix. The sooner we can replicate and fix it, the fewer customers will encounter it.
- When testers encounter crashes, we almost always immediately stop what we are doing and try to replicate that crash. You may or may not have the luxury of time. But if it happens more than once, then you have a reproducible case and can tell us what you were doing.
- Send in your details when you submit your crash files and we’ll debug further to try to find the root cause. As much as you can, share your data and steps with us. Remember that we can use the Anonymize feature in JMP when data is sensitive. If you can provide a set of reproducible steps, we can quickly create a software defect for a developer and hopefully fix it before the release goes production.
How can customers request a new feature or functionality?
For all customer feature requests, please send them to the JMP Wish List where they can post their own request. However, if your customer is not willing to post on the Wish List, or if they are requesting an epic (brand new set of features or brand new way of doing things in JMP), please post on the Internal Wish List.
For Epics, we may need to gather more information, speak to multiple customers in various industries and external thought leaders before an Epic suggestion gets into the pipeline. Many Epics are multi-release projects. Many Epics may also be deemed out of scope for JMP in the near term.
For all external wish list requests, we ask that customer provide the following information:
- What inspired this request?
- Please describe the new or improved feature or solution you would like to see.
- What would the value be to you and/or other users if this new feature is provided?
