THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- You need a JIRA account so if you do not have one then create an account here
- Login to your JIRA account
- Click 'Create' at the top of the screen to create a new issue and a screen form will be displayed for you to fill in
- Project: OFBiz should the default project for the issue. If it is not then please select it from the dropdown selection box
- Issue Type: Bug is the default so please change this if your issue belongs to a different issue type
- Priority: Major is the default priority. Please review the guidelines around assigning a priority and change it if necessary
- Component: Select the OFBiz component that is affected by the issue you are creating
- Affect version: Select the OFBiz version that is affected by the issue you are creating
- Assignee: If you are going to work on this issue yourself the enter your name
- Reporter: The name of the person creating the issue should be automatically default as the reporter
- Environment:
- Description
- Fill in all fields, give as many detail you think necessary
- Generally it is very important to select in the "Affect version" field the ofbiz version you are running. If you are running the trunk then the SVN revision should also be specifyed in the Environment field
- Use the Environment field to specify at least your operating system and the database ofbiz is using since these information could be very useful to help people to work on the issue
- Select the concerned component(s). If all components are affected select ALL_COMPONENTS (uncommon case)
- If you need to attach files such as patches you must do it as a second step after the issue creation. It is also possible to easily attach screenshots to the issue see here
- When attaching files or screenshots you can add a comment where you explain how the attached file is supposed to be used. Please reference the file name in the comment because more files could be attached to the issue at a later time and they will be all listed togheter far from their comments. If, for any reason, you don't want your patch or attachment to be granted to the ASF or committed, please note it in one related comment (possible cases: not ready yet, examples, etc.)
- Also please use preferably .patch as extension for patches. When updating an attached file keep the same name : Jira is able to deal with that and will simply gray old files, you don't need to delete them (sometimes its usefull to compare older patches versions)
- If you provide a patch, be sure to use the button "Provide Patch" (the status will then be "Patch Available"). This allows us (commiters) to know that this issue is ready for review.
- Jira offers a voting mechanism that is used to give more relevance to the issues (see here to learn more)
...