Versions Compared

Key

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

...

Issue TypeDefinition and when to use this type
BugA bug is generally a problem with code or data which is not functioning correctly.
ImprovementAn 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?)

 

Info

Proposal:

  • All potential improvements could start as a Wish.
  • When they have been discussed / reviewed by the community then they can be changed to be an approved New Feature

 

The proposal seems inline with the existing text regarding creating JIRA 

This following text comes from our existing pages re Jira : If you don't have a patch, and you have want to suggest an enhancement or new feature, then discuss this in the dev mailing list instead of creating a Jira issue; at the end of the discussion, the community will consider if a summary of the thread should be saved in a new Jira issue, to facilitate future development

TaskA Task is an action that needs to be carried out that does not fall under any of the other issue types. (NOTE: We have used Tasks in the past - maybe need to specify more clearly when to use....)
TestA Test is a unit test or integrated test
Wish

A Wish is a requirement for new something that does not already exist (What's the difference between this and New Feature?

Info

Proposal:

  • All potential improvements could start as a Wish.
  • When they have been discussed / reviewed by the community then they can be changed to be an approved New Feature

 

The proposal seems inline with the existing text regarding creating JIRA 

This following text comes from our existing pages re Jira : If you don't have a patch, and you have want to suggest an enhancement or new feature, then discuss this in the dev mailing list instead of creating a Jira issue; at the end of the discussion, the community will consider if a summary of the thread should be saved in a new Jira issue, to facilitate future development

 

Sub Task

This task is a child of another JIRA: 

Info

Proposal :

  • To stop using sub tasks for JIRA issues
  • Main reasoning
    • they add to too much detail to an existing task
    • we are adding a level of detail that is not needed
    • if an issue is that complicated that it needs sub-tasks then it may be cleaner and easier for it to be a separate JIRA issue
    • JIRA sprints don't include sub tasks as part of work delivered, so gives a distorted view of actual work performed
    • JIRA issues can remain open for an extended time with only 1 or 2 sub-tasks remaining

...

  • 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 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

...

An issue can have 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 in JIRA to define the OFBiz component or application area.


PLEASE NOTE: That Also be aware that the JIRA labels are shared across all ASF JIRA projects so you will find labels related releated 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:

...