<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>Customizing bugzilla workflow (bug #101179)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">Hi!</FONT></SPAN>
</P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">I would like to see bugzilla's customizable workflow done and I would like to contribute a patch. However, there are some architectural issues I would like to discuss first.</FONT></SPAN></P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">I think the whole workflow should be controlled by an independent module so I could be replaced by something else in specific instalations. If this is allowed we could have BZ easily integrated into more complex enterprise architectures which use other technologies (such as Oracle BPEL).</FONT></SPAN></P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">My main concern about bug #101179 is that I see a "custom workflow" implementation and I see no need for it as most of the work is already done. I don't know much about CPAN's workflow module (Workflow) but I don't have much confidence since its a new module and never heard of anyone using it.</FONT></SPAN></P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">BZ could ship with an implementation of the "abstract" Bugzilla::Workflow module using a solution based on what has been discussed on the bug.</FONT></SPAN></P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">In what features are concerted, I think we should support:</FONT></SPAN>
<BR><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">a) Internally, each bug should have a process number (this allows mapping into other workflow systems);</FONT></SPAN>
<BR><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">b) The workflow module should be able to define a number of fields that characterize each state (currently, status + resolution);</FONT></SPAN></P>
<P><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">c) User actions (accept, reassign, resolve) for each bug are determined by the workflow module;</FONT></SPAN>
<BR><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">d) All changes that occur after a user action are determined by the workflow module (default will just change state, invoke some mail sending and register the bug activity);</FONT></SPAN></P>
<P><SPAN LANG="pt"><FONT SIZE=2 FACE="Arial">A few things I would like to discuss is:</FONT></SPAN>
<BR><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">e) How do we start processes? The products page could be replaced by a "workflows" page (the default module can have a different workflow per product) but more complex systems could have several workflows per product;</FONT></SPAN></P>
<P><SPAN LANG="pt"> <FONT SIZE=2 FACE="Arial">f) Should we control which fields can be edited in which workflow state?</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Any ideas?</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Paulo</FONT></SPAN>
</P>
</BODY>
</HTML>