[Koha-devel] Proposal to change Bugzilla Status and Patch Status values

[Nicole Engard]

+1

On Fri, Jan 6, 2012 at 9:40 AM, Chris Nighswonger <
cnighswonger at foundations.edu> wrote:

> +1 here.
>
> 2012/1/6 Ian Walls <ian.walls at bywatersolutions.com>:
> > Fellow Koha-ckers,
> >
> >
> > A comment on bug 7167
> > (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167) has
> gotten
> > my interest re-awakened about a proposed Bugzilla revision that had been
> > floated earlier this release cycle.
> >
> > I'd like to remove Patch Status, and move all those values to the regular
> > Status field.  This has the following advantages:
> >
> > Status is a built-in field, so it's got much richer support in Bugzilla.
> > For example, status workflows can be added.  Patch Status is a custom
> field,
> > and is just a list of values
> > We would no longer lose the Priority value of a bug by having to set it
> to
> > Patch Sent in order to get the Patch Status values visible
> > Statuses can be updated as part of submitting an attachment like a patch,
> > streamlining the patch submission process (fewer clicks to keep all the
> > fields up to date).
> >
> > I'd also like to add a new status, "In Discussion", for bug reports that
> > have deeper procedural, philsophical or technical implications outside
> that
> > of mere coding (bug 7167 being an example).
> >
> > We're not using Status for anything else, so there is no trade-off there.
> > This is really how the Status field is meant to be used.  We will,
> however,
> > have to rebuild the canned searches that look for patches that Need
> Signoff,
> > are Signed Off, and are Passed QA/Failed QA.
> >
> > The other difficulty of this proposal is that we'll need to turn off
> > automatic bug emails for a bit while we make the bulk changes to the
> Patch
> > Statuses; otherwise, we'll all get spammed to high heaven with
> meaningless
> > updates when the migration occurs.
> >
> > What do people think?  Does this sound like a reasonable change to make?
> > Any objections?
> >
> > Cheers,
> >
> >
> > -Ian
> >
> >
> > -- Ian Walls
> >
> > Lead Development Specialist
> > ByWater Solutions
> > ALA Midwinter Booth #2048
> > Phone # (888) 900-8944
> > http://bywatersolutions.com
> > ian.walls at bywatersolutions.com
> > Twitter: @sekjal
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > 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/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> 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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20120106/1bfdc00b/attachment.htm>