THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Issue Type | Definition and when to use this type |
|---|---|
| Bug | A bug is generally a problem with code or data which is not functioning correctly. |
| Improvement | An improvement is something that enhances the functionality of an existing feature |
| New Feature | New functionality that does not already exist - (What is the difference between this and Wish?) |
| Task | |
| Test | |
| Wish | New functionality that does not already exist - (What's the difference between this and New Feature?) |
| Sub Task | This task is a child of another JIRA (NOTE: We use sub-tasks but not Tasks.....) |
Description
The issue description is the most important part of the JIRA issue.
...
All JIRA issues need a priority as it determines what needs to be worked on. This is important because it helps to ensure that the community is focussed and working on the right tasks.
| Priority | Current JIRA Definition | Proposed Revised Definition and when to to use this priority |
|---|---|---|
| Blocker | Blocks development and/or testing work, production could not run | A blocking issue an issue with a released OFBiz version that does not run, does not comply with legal requirements, is a security vulnerability to users or exposes the project and Apache Software Foundation to significant risk |
| Critical | Crashes,loss of data, severe memory leak | A critical issue is an issue with a released OFBiz version that causes the system to be crash, become unstable, unusable, or lose data and has no workaround. |
| Major | Major loss of function | A major issue is an issue with a released OFBiz version that has a significant impact due to loss of function and has no or limited workarounds |
| Minor | Minor loss of function or problem where easy workaround is present | A minor issue is an issue with a released OFBiz version, an unreleased branch or trunk that has isolated impact but workarounds are available |
| Trivial | Cosmetic problem like misspelt words or misaligned text | A trivial issue is an issue with a release released OFBiz version, an unreleased branch or trunk that are cosmetic or do not change the functionality |
...
Issues can be classified using the label. For example an issue can be labelled as 'Beginner' indicating that it is suitable for beginners or newcomers who want to begin contributing to OFBiz.
Do we have a list of labels that we could use?
Reporter
The issue reporter is automatically assigned by JIRA based on the user profile of the person creating the Jira
...
If you are an Assignee for an issue and you have completed your work then once you have updated the JIRA details or comments, please unassign yourself from the issue. This is important if the work is a patch that needs to be committed. Our Committers will be able to see the unassigned tasks that are available to be picked up, review them and if necessary commit them
Component
Flags
Patch or Important
Status
NOTE: Do we need a 'Testing' status..?
...
Watching a JIRA Issue
OFBiz JIRA Workflow
What are the JIRA Tags and how to use itEpics are disabled - do we enable them?
Add a wiki page (if one does not exist) documenting:
- Guidelines for writing JIRA mentioning clarity, provision of solution.
- A clear definition of priorities (blocker, critical, major, minor,
trivial) with some examples.
- A description of meaning of assignee and how to use it
- A description of other metadata and how to properly use it (tags,
components, affects version, etc...)
...