Page History

...

• 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 issues
  

Instead please post your question or comments on our user or development mailing lists and someone from our community will respond to you.

Discussion Point

• If you have an idea for a new feature or improvement
  
  •  If you don't have a patch, and you 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
  • 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

Instead please post your question or comments on our user or development mailing lists 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'

...

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 discovered a bug that has not yet been reported
• If you have identified a bug then 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) 
• If you have discovered a bug that has not yet been reportedIf after a community mailing list discussion the recommendation is the create a JIra (e.g. new features, improvements etc)

...

 if, on the other hand, you don't have time to do this, (i.e. to discuss the design solution with the community) 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

• Doing this means that patches for improvements and new features can get uploaded to JIRA and the community has not discussed or agreed they want them or are necessary
• Are we trying to use JIRA like a patch code repository too? If so then is JIRA the best place to do it? How do we make the distinction between patches that are contributed and are accepted to the repository and those that are not acceptable due to whatever reasons (coding, design etc)

1. Summarizing:

• Bugs: always create a new Jira issue everytime you find a new bug
• New features/enhancements: create new Jira issue only if you have a patch (or if you plan to submit it very soon)

...

How to Create a JIRA Issue

How to create a Jira issue

...