[geeklog-devel] Bugtracker workflow suggestions

[Vincent Furia]

I think an ideal solution would be something that would be obvious to those
submitting a patch. Changing the category to Patch will work for those who
are familiar with our system, but would be non-obvious for everyone else.
I'm not sure there is a good solution though...

-Vinny

On Sat, Jan 15, 2011 at 07:59, Dirk Haun <dirk at haun-online.de> wrote:

> We have quite a few issues in our bugtracker now with an attached patch.
> However, they aren't easy to find. As a result, they tend to get overlooked.
> In other words: Many issues in our bugtracker have already been solved - but
> we don't see it since the existence of a patch isn't easily visible.
>
> There doesn't seem to be an easy way to extend the workflow with an
> additional state (say, "has patch"). So far, we've tried to work around the
> problem by setting the status of such an issue to "assigned". But that
> hasn't happened for all the issues with a patch and it still doesn't help to
> find all issues with a patch, since you would also get issues that are
> assigned to people currently working on it.
>
> We do, however, have a third category (besides "bugs" and "feature
> requests"): "Patches".
>
> Suggestion: An issue for which we have a patch will be changed to category
> "Patches". That makes them easier to find (use the filters). The only
> downside is that we're losing the information whether it was a bug or
> feature request to begin with. But then again that information can still be
> seen in the issue's history.
>
> Any objections or other suggestions?
>
> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110115/91b5719e/attachment.html>