#194: Examine workflow for Bloodhound site ------------------------+-------------------- Reporter: gjm | Owner: nobody Type: task | Status: new Priority: major | Milestone: Component: siteadmin | Version: Resolution: | Keywords: ------------------------+--------------------
Comment (by gjm): I've been looking into various issues around workflow. One thing that the [https://issues.apache.org/bloodhound/attachment/ticket/194/opensource- workflow.png opensource workflow] is missing for us is capturing aspects of review/testing. I am not entirely sure that we need anything specific for testing so I suggest that we just have a generic review step that is re-entrant in case anyone wants to record specific testing to be done by another user. Also, I am not proposing that there should be anything to force the ticket to go through these steps - it is more so that the ticket can be in an appropriate state for others to pick up on. So, the rules I am suggesting at the moment are in the attachment:new_workflow.ini which should look something like this as a graph: [[Image(opensource workflow with review.png)]] The graph misses a few features like where there is change of ownership which I have added to the changes to the infoneeded and review states for the moment. -- Ticket URL: <https://issues.apache.org/bloodhound/ticket/194#comment:13> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound (incubating) issue tracker