Bug tracking system

Hi everyone,

On the topic of defect tracking: the tech committee has elected to try using JIRA to track bugs. I started to put together a set of objectives and design, maybe got a bit carried away. Please take a look at this wiki page and share your comments. I believe our goal should to have a simple bug tracking system that we can grow and adopt as the need arises.

There could be some overlap or confusion as we have several organizations working on projects (MOZ and TZ), with the 2.0 branch acting as a melting pot between the two. This means bugs from each project may also appear in 2.0, but potentially tracked and fixed in those projects. Each project is using their own bug tracker, and thus the OpenLMIS JIRA is not appropriate to track these project-specific bugs, nor do we want to encourage duplicate bugs in various systems. The OpenLMIS JIRA should track issues for the core or base application

We have encountered a few bugs that maybe should be in the common JIRA. Bugs relating to stock management, shared between the two projects, should be reflected in the common JIRA.

The actual JIRA project is here: https://openlmis.atlassian.net/projects/OLMIS/summary

Rich

Thanks Rich for setting it up!

···

On 6 November 2015 at 01:18, Rich Magnuson rich.magnuson@villagereach.org wrote:

Hi everyone,

On the topic of defect tracking: the tech committee has elected to try using JIRA to track bugs. I started to put together a set of objectives and design, maybe got a bit carried away. Please take a look at this wiki page and share your comments. I believe our goal should to have a simple bug tracking system that we can grow and adopt as the need arises.

There could be some overlap or confusion as we have several organizations working on projects (MOZ and TZ), with the 2.0 branch acting as a melting pot between the two. This means bugs from each project may also appear in 2.0, but potentially tracked and fixed in those projects. Each project is using their own bug tracker, and thus the OpenLMIS JIRA is not appropriate to track these project-specific bugs, nor do we want to encourage duplicate bugs in various systems. The OpenLMIS JIRA should track issues for the core or base application

We have encountered a few bugs that maybe should be in the common JIRA. Bugs relating to stock management, shared between the two projects, should be reflected in the common JIRA.

The actual JIRA project is here: https://openlmis.atlassian.net/projects/OLMIS/summary

Rich

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/eadd4caf-1e86-417d-b1fb-542b7c513320%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jeff Xiong
ThoughtWorks
+86 186 826 53819