Question is not an IssueIf you have a question do not create an issue from that. We are answering questions on Forum.
If your meter is not answering, it's not an issue, it's a question. There are several meter settings that might cause it.
How to create a good issueThis page details the process for creating a well-crafted issue report. This will help you get progress faster, because it makes it easier for others to help you!
Before you open an issueTry first to search the issue queue first. Make also sure that you have selected the right program version.
TitleYour title should be descriptive and concise. Explain the error shortly.
ProjectIn most cases Project will be automatically populated. Make sure this is correct. Do not try to add ANSI C issues to Delphi, etc.
VersionWhen reporting a bug, be sure to specify the version where you found the bug. To best help the developers, upgrade to the latest official release and verify the bug still exists.
ComponentSelect is the issue on code, documentation, or user interface.
CategoryA category determines the broad grouping under which your issue falls. Defining the category for an issue.
PriorityPriority is used to define the relative importance of your issue to the project and other issues in the queue. It does not define the importance of the issue to you personally.
- Critical is used to designate broken functionality that makes the project unusable (e.g. data loss, data corruption). "Critical" should be reserved for the most problematic and important issues. Abuse of the Critical field will likely get your issue ignored by a developer.
- Major is used for issues that have significant repercussions but do not render the whole system unusable.
- Normal is the default priority applied.
- Minor is when there is no urgency to solve the issue.