Please see the following wiki page for guidelines on how to create an issue: How to report an issue
Developers don't use the various issue states consistently. The following description just gives a broad overview. See here for a description of states in JIRA.
If an issue is considered to be a Duplicate, it will be marked as resolved, and the original issue will be linked. It's not always the newer issue that gets closed as duplicate, sometimes it's the older one, e.g. when the description in the new one is better, or the new one has more watchers. This depends on the developer resolving as duplicate. Duplicate issues should only be reopened when you have determined that they are not actually a duplicate of the linked issue, and for no other reason.
Issues may be found to be Won't Fix or Not a Defect for various reasons, e.g. when a developer determines that the issue isn't actually a problem with Jenkins.
Issues may be resolved as Cannot Reproduce when the developer is unable to reproduce the issue as described, e.g. because it may have been resolved since it was reported, or it is believed the issue is not with Jenkins.
Issues resolved as Incomplete do not provide a sufficient description of the problem.
When a developer decides to work on such an issue, the Assignee field is changed to that developer. It may be set to In progress while it's being worked on.
When a fix has been integrated, the issue is usually marked Resolved (using the resolution Fixed), and sometimes marked Closed after the fix has been verified.
Skip to end of metadata Go to start of metadata