Versions Compared

Old Version 64

changes.mady.by.user Sharan Foga

Saved on

compared with

New Version 65

changes.mady.by.user Sharan Foga

Saved on

Key

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

...

If you want to find out more about how JIRA works then please see the link to the complete JIRA documentation

 

JIRA Fields and Meta Data

...

Other examples of good JIRA summaries

  • Create a separate SVN repository for OFBiz official plugins
  • Add the auto-entity CRUD services for Runtimedata
  • View Sales Order throws exception in getReturnableQuantity
  • Not able to select virtual products in WebPos

 

Info

Proposal:

  • Review existing JIRA summaries for issues that are open / unresolved
  • We ask the creator to tidy up any unclear summaries

...

The issue description is the most important part of the JIRA issue as . If you are reporting a bug or problem then it provides information that will allow someone else to investigate and resolve it. It must be written in such a way that it is clear enough for someone to easily replicate the problem. This means that you need to include information about:

  • What you did (e.g what application, screen, and the highlight the steps you went through etc) 
  • What you were expecting to happen
  • What actually happened

In some case cases you might already have an idea about what is causing the issue is and if . If so then please include your suggestions as to the cause as this may be helpful to the person picking up the issue.

e.

Issue Description Examples:

g (ADD AN EXAMPLE)




If the issue is about some work that is planned (e.g refactoring, documentation etc) or agreed after a community discussion then please use the description is used to highlight the steps needed to get the work done. Add a reference back to the community discussion if relevant.

ExampleImplementation of Specific Functiona


This issue is related to the discussion found in this thread in which the community approved restructuring our repositories. To achieve this task the following needs to be done (in this order)

  1. Update the gradle scripts to assume that no plugins exist in the plugins directory by default and no component-load.xml exists. It should follow the same logic in loading the components as found in the ComponentContainer class. Also the activation and deactivation of plugins happens in ofbiz-component.xml, not in component-load.xml
  2. Add a new task to gradle called pullPluginSource that retrieves a plugin from subversion and defaults to the official plugins repository of Apache OFBiz. This task mostly server "Trunk" because it always needs the latest source code of the plugins.
  3. delete plugins/component-load.xml
  4. move all plugins to a new repository called http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins
  5. move the core framework to a new repository called http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
  6. fix buildbot to point to the new framework location
  7. update documentation where applicable including README.md



Priority

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.

...