THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Status | Definition |
|---|---|
| Open | This status indicates that the issue is open and is the default status when a JIRA issue is created |
| In Progress | This status indicates that the issue is in progress and that someone is working on it |
| Reopened | This status indicates that the issue has been previously closed but has to be re-opened because of some additional work |
| Resolved | This status indicates that the issue has been resolved. If the issue is code or patch related then it also indicates that the code has been committed |
| Closed | This status indicates that the issue has been closed. It can indicate issue completion or simply the closure of an invalid issue |
| Patch Available | This status indicates that the issue has a code patch uploaded that will resolve the issue. |
Affect Versions
Fix Versions
Creating a JIRA Issue
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. Also 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.
| Info |
|---|
| IMPORTANT NOTE: If you have a question about how OFBiz works, which version to use or anything related to your specific implementation that you would like some advice or help from the community on, then please do not create a JIRA issue. Instead please post your question or comments on our user or development mailing lists |
How to create a Jira issue
- Create an account here, if you do not have one
- Login
- (optional if you are sure it's new) Search if an issue for what you are after already exists by using the "Find issues"
- (optional if you are sure it's new) If an issue on the subject already exists you can add a comment on it
- If a issue does not exist, create a new one selecting the "create new issue" command. For details on the issue creation see here
- Select the OFBiz project and the issue type.
- 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)
Commenting on a JIRA Issue
...