Issue tracker

> JMeter uses Bugzilla for issue tracking, i.e. for reporting bugs and requesting enhancements.

> Before creating a new issue, please check whether the issue has already been reported by searching Bugzilla. It's also worth checking first on the JMeter user mailing list; others may already have a solution.

Known Bugs

> - Bugzilla - All open bugs
> - Bugzilla - Open bugs (excluding enhancements)
> - Bugzilla - Enhancements only

Requesting an enhancement

> In most cases it is worth starting a discussion on the mailing list first. Bugzilla is good for tracking progress and supplying patches, but is unwieldy for longer discussions.

> If you have not already done so, you need to register an account first, using the "New Account" link at the top of the main Bugzilla page: https://issues.apache.org/bugzilla/ .

> Make sure you read and understand the information on the account creation page before signing up.

> Once logged in, click "File a bug" and select JMeter from the list Please set the severity to "enhancement".

> Please make sure that you describe the enhancement in sufficient detail. If necessary provide an example use-case.

> If you are providing a code patch, also provide a test case, and documentation on how to use the new feature (ideally as a documentation patch).

Raising an Issue

> First check that the issue has not already been reported. If reporting a bug, are you sure it really is a bug in JMeter, not just a misunderstanding of how JMeter works?

> If you have not already done so, you need to register an account first, using the "New Account" link at the top of the main Bugzilla page: https://issues.apache.org/bugzilla/ .

> Make sure you read and understand the information on the account creation page before signing up.

> Once logged in, click "File a bug" and select JMeter from the list.

Required Information for bug reporting

> Please make sure you provide sufficient information for others to be able to make use of the report effectively. Use the checklist below to guide you.

> - JMeter version
> - Java version (output from java -version)
> - OS version
> - jmeter.log file (unlikely to contain sensitive information, but check before uploading)
> - JMX file if relevant (redact any sensitive information first), providing a simplified Test Plan (using DEBUG sampler) will ensure BUG is fixed much more rapidely than without it
> - JTL file if relevant (may need to redact sensitive information)
> - For a suspected bug, describe what you did, what happened, and how this differs from what you expected to happen. Does it happen every time?.
> - Add yourself in CC List to be notified when JMeter Team requires more information (in this case bug will be marked as NEEDINFO)
> - Select accurately the IMPORTANCE level, ENHANCEMENT means it's not a BUG while others mean it's a BUG
> - If you are providing a patch to fix a bug, please ensure it is in unified diff format. If using Eclipse, please set the patch root to "Project", not the default "Workspace" which is harder to apply.
> - New source files can be provided as is; please ensure they have the standard Apache License header (as per other JMeter files). Please do not use @author tags (credit will be given in the changes file).
> - In the case of patches for new features, please also provide documentation patches if at all possible. Components are documented in xdocs/usermanual/component_reference.xml.

> See also the following Bug writing guidelines , also the terms and conditions noted on the Bugzilla account creation page.

Copyright © 1999-2016, Apache Software Foundation
Apache, Apache JMeter, JMeter, the Apache feather, and the Apache JMeter logo are trademarks of the Apache Software Foundation.