Page History

...

Creating issues in JIRA adds to the project workload so it is important that they are created when needed and with the right level of information that will help someone to pick it up and resolve it as soon as possible.

When Not to

...

Create a Jira Issue

• If you want general OFBiz help or advice
• If you want to know which version to use
• If you want to talk about anything related to your specific OFBiz implementation
• If you want to know how other users manage a process or function
• If the issue has already been reported and exists in the current list of issues
  

Instead please post your question or comments on our user or development mailing lists

When  to create a Jira 

many people are using OFBiz so before creating a new JIRA always check that the issue you are reporting hasn't already been created. You can do this using the search issue functionality in JIRA.

1. Before creating any Jira issue, please check, using some related key words, if a similar issue does not exist already. For that you can first use the quich search at top right of Jira pages and after refine your search using relevant information. For instance by default all projects are scanned, you may then search only in OFBiz, etc.

...

and someone from our community will respond to you.

Many people use OFBiz so there is a chance that issue you have encountered may have already been reported. You can search JIRA using the keyword search to see if anything with a similar topic has been created. There is a 'Search' box in the top right of the main JIRA screen and this searches across all ASF projects. All OFBiz issues have the format 'OFBIZ-9999'

Another way to search issues is by clicking the 'Issues' link on the left hand column and then 'All Issues'. An advanced search query filter box is displayed that allows the user to enter their search criteria. The query box is user friendly and offers interactive lookup on the query commands as you type. See below for an example of a query to find all issues that have the word 'accounts' in their description

project = OFBIZ and description ~accounts

When  to Create a Jira Issue

Reminder: Before creating a JIRA issue, please check that it has not already been reported.

If you have identified an issue and also fixed it, and want to contribute the fix back to the project then you can create an issue and attach your patch to it. (Note if the issue has already been created then attach your patch to the existing issue and do not create a jira) 

When to create a Jira issue

...

1. If you already have a patch for an improvement/fix then create a Jira issue (if there is not one already) and attach your patch to it
2. If you don't have a patch, and you have discovered a bug, create a Jira issue (if there is not one already) providing as much details as possible (including the rev. number and the environment you are using, and the step to recreate the bug). if you have no ideas how to describe the bug use this template
   1. What you did (including detailed steps to reproduce)
   2. What you expected to happen
   3. What actually happened (including exact quotes of error messages, etc)
   4. If possible provide an URL
3. If you don't have a patch, and you have want to suggest an enhancement or new feature, then discuss this in the dev mailing list instead of creating a Jira issue; at the end of the discussion, the community will consider if a summary of the thread should be saved in a new Jira issue, to facilitate future development
4. If you don't have a patch, but you are planning to work on it, and you want to share your design details with the community, you should discuss this in the mailing list instead of creating a Jira issue; if, on the other hand, you don't have time to do this, you have already decided that you want to implement your patch following your design notes, and you just want to let the community know about the upcoming patch, you can create a Jira issue (to which you will attach your patch when it is ready);
   Summarizing:

...