The Jenkins JIRA is not a support site. If you need assistance or have general questions, visit us in chat, or email one of the mailing lists.

Before creating an issue

First, determine what kind of issue it is. There are three main types whose use is explained on this page:

Other types (Patch, Task) are not widely used in JIRA. Neither will be explained here. If you want to propose a patch, create an issue of one of the 3 types above and then create a pull request in GitHub.

Before reporting a bug

If you're still unable to resolve the problem and cannot find existing issue reports or related fixes in newer versions of Jenkins or the plugins, file a bug in JIRA.

Before requesting an improvement or feature

If you cannot find anything, file an improvement or new feature request in JIRA.

That you're searching for existing issues doesn't just make it easier for us to deal with any issue reports, but it will also show which issues are considered important by the community by the number of voters and watchers (and therefore increase the likelihood of related changes). It's not that obvious when an issue has been reported separately several times with only a few watchers each.

Creating the issue

You need to register an account if you haven't already. Then, just select Create Issue on the JIRA home page.

What information to provide for Environment and Description

Much of the advice on How To Ask Questions The Smart Way also helps you write great issue reports.

Environment is mostly relevant for bug reports: What is the configuration experiencing the issue? Depending on the type of problem, the following are often relevant:

If this is too much information for the Environment field, just put some of it into the description.

Every Jenkins installation has the /systemInfo URL with information about Jenkins. If you're not sure what information to provide, copying everything on that page is a good place to start. Another option would be to install the Support Core Plugin, which allows downloading zip files from Jenkins that contain information relevant for investigating bug reports.

The Description should be comprehensive to allow others to understand the problem or improvement request immediately. A few suggestions on what to include (again, mostly applicable to bug reports):

After creating the issue

Once you've created an issue, make sure to respond to requests for additional information in a timely manner, otherwise your issue may be resolved as Incomplete.

If you reported a regression in Jenkins (i.e. a bug that appeared after updating Jenkins itself), consider leaving community feedback on the changelog to let others know about it.

Keep the issue updated. This includes, for example: