...
| Note |
|---|
| title | When to create a Jira issue |
|---|
|
- 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.
- When you find a duplicate of a JIRA issue, please close the newer one with the resolution 'Duplicate', and state what the original issue is. This does not apply for placeholder issues or if the newer Jira does contain additional aspects or more comprehensive solutions, documentation or patches. If in doubt, please discuss on the development mailing list before choosing one issue over the other.
- 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
- 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
- What you did (including detailed steps to reproduce)
- What you expected to happen
- What actually happened (including exact quotes of error messages, etc)
- If possible provide an URL
- 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
- 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:
- 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)
|
| Info |
|---|
| title | How to work with Confluence (by order of preference) |
|---|
|
- If you are a registered wiki contributor (recommended) you can edit any page in the wiki, just be sure to add a sentence about what you did when commiting.
- If you are not a registered wiki contributor and don't want to be one, you can still add your Confluence formatted contents as comments in existing pages. So if you need a new page you need to ask for its creation before adding comments...
- If you don't want to provide Confluence formatted user stories then open a Jira and add your unformatted user stories in a text file
|
Following changes
Please read this section in OFBiz Committers Roles and Responsibilities page
...