[geeklog-devel] Bugtracker workflow suggestions

[Kalpa Welivitigoda]

On Sat, Jan 15, 2011 at 8:29 PM, 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?
>

Well, do we do the change of category soon after a patch is uploaded
or once it gets reviewed?

> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>



-- 
Best Regards,

Kalpa Pathum Welivitigoda
http://kalpapathum.blogspot.com
http://thiraya.wordpress.com
http://www.flickr.com/photos/49383144@N05/