Community
Participate
Working Groups
Considering the vast usage of bugzilla for various tasks (bugs, tasks, code review), it would be good to allow for customized workflows for any given product/component. Defaulting to the default workflow where not specified.
Could you provide more details what kind of workflow you have in mind?
I am using bugzilla to track a multitude of issues, many of which code follow the default bug status workflow. Others of which are hosted on the same bugzilla installation require different status workflows. An example of this is a review system for code changes. Although there are other tools that might perform this, bugzilla can handle this as a status work flow. An example workflow for code review migh be something like: Review Request Information Required Accepted Denied The point is that the default status flow may or may not apply to all product entries and it would make it entirely flexible to be able to customize this by product, product/category and all those that are not specified should be simply take the default.
Frank, do you know to which extend this is already supported?
(In reply to comment #3) > Frank, do you know to which extend this is already supported? No bugzilla has no support for this in an single instance. If you define more then one Instance you can so this.
Darren, do you have a custom Bugzilla instance that allows separate workflows per product or am I misunderstanding the request?
I don't think I should require different instances. I should be able to manage this all in a single instance. I have all my product/components within a single instance currently.
The Bugzilla connector already supports custom workflows: http://wiki.eclipse.org/Mylyn/Bugzilla_Connector#Custom_Transitions. Does that work for you?
So this is great, but this custom workflow/transition, when applied, is applied to all product/component. It would be ideal to specify which each (multiple flows) flow per product (encompassing all subproducts or components) or specifically a product/component (if need be). Ideally this would not override the 'default' flow for products that are not specified. Example (potentially). Flow=flow1 Product=Product1 CustomStatusNames=true DuplicateStatus=CLOSED StartStatus=UNCONFIRMED ClosedCustomStatus=RESOLVED ClosedCustomStatus=VERIFIED ClosedCustomStatus=POST <transitions> name :UNCONFIRMED:, can_change_to :NEW,POST,CLOSED: name :NEW:, can_change_to :POST,CLOSED: Flow=flow2 Product=Product2 CustomStatusNames=true DuplicateStatus=CLOSED StartStatus=UNCONFIRMED ClosedCustomStatus=RESOLVED ClosedCustomStatus=VERIFIED ClosedCustomStatus=POST <transitions> name :UNCONFIRMED:, can_change_to :NEW,POST,CLOSED: name :NEW:, can_change_to :POST,CLOSED: And say if product three is available, it should just take the default flow. The above flows are identical, but in reality would most likely be unique. Not sure if this is clear, but this would be a better solution than having multiple individually managed instances?
I am afraid I am still not quite understanding this request. My understanding is that Bugzilla only supports a global workflow configuration but does not support custom workflows on a per product basis. The standard type of workflow customization is supported in Mylyn. Can you clarify whether your Bugzilla instance supports per product workflow customizations? If so, can you point me at the corresponding documentation? If you are asking for configuration of workflows on the client side that is not available on the server side it's very unlikely that we would support that.
I believe this to be mylyn side. Sorry for the confusion. The configuration file (customized (Workflow description file) is not configurable on a per product basis. All mylyn repositories seem to have a product/component requirement. The customization file would be as described in comment #8. In order to provide a customized transition for a specific product the customization file would need a different template or structure that would allow for multiple flows to be described and allow for a default flow to be applied to products that are not covered by describe custom flows.
The custom workflow file is intended to describe the workflow that is present on the server side but not intended for client side configuration that goes beyond that. It is out of scope of the Mylyn project to provide that kind of customization for the Bugzilla connector.
If this is the case, the connector should only read the work flow configuration from the bugzilla server and not allow a localized (client) workflow. Having this on both sides provides a synchronization issue and multiple points of configuration. The connector should ideally only connect and configure from the server (similar to customized fields etc...). Is this the case? It seems unclear. The custom workflow seems to be local on the client, and at the same time, allowance for xmlrpc.cgi is available (server side, but not documented to provide custom work flows). Should it be that the connector only receives configuration from the server?
(In reply to comment #12) > Should it be that the connector only receives configuration from the server? Yes, that would be the best solution and we are working towards removing any manual configuration. Unfortunately older Bugzilla releases did not provide workflow configuration and hence the setting to provide a local configuration file was introduced to allow use of Mylyn with installations that have customized workflows. In the common case Mylyn you should be able to obtain the configuration through XML-RPC and there should not be a need for the configuration file.
