[almighty] priority driven model for issue tracking

[Thomas Mäder]

I just wonder how the approach scales to large projects. What do you do 
with bug reports that you can't get to right now...just abandon them? 
Way to value your customers that were nice enough to actually report a 
bug...

Part of the approach seems to be that the have a engineering tracker and 
then the "real" issue tracker somewhere on the side (left as an exercise...)

/Thomas


Am 05.08.2016 um 16:10 schrieb Max Rydahl Andersen:
> Hey,
>
> spotted this article today: 
> http://blog.gitprime.com/a-priority-driven-model-for-issue-tracking/
>
> Pretty interesting read and it captures one of the concerns I always 
> have when I see the number of ideas, bugs, tasks etc. flowing into an 
> planning tool or issue tracker - it will just overwhelm you if things 
> are not nurtured.
>
> In this they very aggressively say that anything not precise enough or 
> too old gets removed from the engineering issue tracker.
>
> This article nicely illustrate the importance of not cluttering your 
> system - I do see that we need in almighty be careful about how we 
> present the workitems and that we do not require a lot of process hell 
> to keep it uptodate.
>
> In PDD terms - might be that board views by default filter out higher 
> level work items and just provide a link to them. Basic stuff like that.
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public