Page History

...

JIRA is the tool that we use to track project related work. This includes ideas for improvements, non code based work such as testing and documentation as well as bug fixes and issues. (Please see the following link for the OFBiz JIRA Summary Panel.

Note:All of these types of work are currently referred to as a 'JIRA Issue' which may sometimes cause confusion).

Please If you want to find out more about how JIRA works then please see the following link for the OFBiz JIRA Summary Panellink to the complete JIRA documentation

JIRA also provides a list of tasks that need to be actioned in the form of a TODO list, which can be sorted by a range of categories including priority and person assigned. It also can be used to generate statistics about work in progress and issue resolution.

...

How to Create a JIRA Issue

1. You need a JIRA account so if you do not have one then create an account here
2. Login to your JIRA account
3. Click 'Create' at the top of the screen to create a new issueNew Issuecreate a new one selecting the "create new issue" command. For details on the issue creation see here
4. Select the OFBiz project and the issue type.
5. 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)
6. 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.
7. Jira offers a voting mechanism that is used to give more relevance to the issues (see here to learn more)

How to Update a JIRA Issue

1. You need a JIRA account so if you do not have one then create an account here
2. Login to your JIRA account
3. 
   
   1. (optional if you are sure it's new) Search if an issue for what you are after already exists by using the "Find issues"
   2. (optional if you are sure it's new) If an issue on the subject already exists you can add a comment on it
4. If a issue does not exist, create a new one selecting the "create new issue" command. For details on the issue creation see here
5. Select the OFBiz project and the issue type.
6. 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)
7. 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.

How to create a Jira issue

...