...
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.
- OFBiz has several versions of the code base available as released and unreleased branches, as well as the
...
- trunk and JIRA covers all of them.
- Blocking and Critical issues are generally reserved for problems
...
- with production systems (i.e systems that customers use). The OFBiz 'production systems' are our officially released versions that The highest priority of work the project
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, causes the system to crash, is 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 crash, become unstable, 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 released OFBiz version, an unreleased branch or trunk that are cosmetic or do not change the functionality |
...