> For tagging / monitoring, I'm ok with having the default = NO, but
> for the official bug tracker, I would like it to be YES. The reason
> is that I want any activity done a user on an old issue to cause it to
> go to the top so that we can see it. This may be less of an issue
> once the voting feature is added and it updates the timestamps as
> customers vote for the features.
I think this would be a weak technical solution for a social/workflow problem.
In my view the problem is that there are 2480 open issues and there is now workflow how these should be prioritized.
The "tagging/monitoring -> update" suggestion would be a valid workaround. But I think a weak one,
1. as there may be important open issues got lost by this
2. and it could lead to users tagging/unmonitoring/monitoring their issues to keep them at the top :-)
My suggestion would be that it should be an important task of the workflow that whenever some developer looks at a bug he should change it from new->acknowledged and tries to set a priority. Bravely. A wrong priority is better than none.
Then ordering could be done by priority.
Perhaps you could also ask for supporters that help only for this specific task: Prioritizing issues.
P.S. Thanks for mantis!
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@...
Get latest updates about Open Source Projects, Conferences and News.