Versions Compared

Old Version 70

changes.mady.by.user Sharan Foga

Saved on

compared with

New Version 71

changes.mady.by.user Sharan Foga

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 have been signed and approved for release and issues here are     high the highest priority.


 

 

PriorityCurrent JIRA DefinitionProposed Revised Definition and when to to use this priority
BlockerBlocks 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

CriticalCrashes,loss of data, severe memory leakA critical issue is an issue with a released OFBiz version that causes the system to crash, become unstable, lose data and has no workaround.
MajorMajor 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

Info
NOTE: Generally none of the unreleased branches or the trunk will have this issue priority unless there are outstanding major issues with a released OFBiz version and the fixes need to be implemented within the unreleased branch or trunk
MinorMinor loss of function or problem where easy workaround is presentA minor issue is an issue with a released OFBiz version, an unreleased branch or trunk that has isolated impact but workarounds are available
TrivialCosmetic problem like misspelt words or misaligned textA trivial issue is an issue with a released OFBiz version, an unreleased branch or trunk that are cosmetic or do not change the functionality

...

Labels are a way to classify issues. 

  • 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, or 'Documentation' for document related tasks.

An issue can have mulitple labels more than one label and JIRA allows you to create new labels automatically if the one you need does not already exist.  Please be careful that you are not using the label as an indicator for the OFBiz 'Component'  as we already have a component field to define the OFBiz component or application area.

. (PLEASE NOTE: That JIRA labels are shared across all ASF projects so you will find labels related to other projects in the drop down selection box._)

NOTE: We need to be careful that we are not using the label as an indicator for the Component as we already have a Component field to define the OFBiz component or application area.

 

Info

Proposal

  • Define a list of standard labels that we can use to classify our issues:

 

 

To refine the use of labels it may be easier to define the ones that we want to use:

...

Do we have a list of labels that we could use and can we extract the existing list from Jira?

NOTE: We need to be careful that we are not using the label as an indicator for the Component as we already have a Component field to define the OFBiz component or application area. 

Reporter

The issue reporter is automatically assigned by JIRA based on the user profile of the person creating the Jira

...