Paul Poulain <[email protected]> > And the workflow would finally be: > NEW > Patch sent > signed-off > passed QA > resolved (pushed) > fixed > > many/most projects work this way I think. Once a patch has been applied, > the problem is resolved from dev point of view. The reporter just > confirm by marking "FIXED".
I don't mind but I would really like the bugzilla workflow to match the intended workflow. It confuses me a bit that we move into the patch status attribute and the person who sets the final state in that (the RM, patch pushed) does not change the main status at all... and I suspect I am not alone if there are many bugs stuck in the Assigned+Pushed state. This would have the benefit of making the bugzilla-produced report tables more useful, too. A backport-needed status may be a good move for that, too. Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/ _______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
