I really don't like the bundle-of-tagged-issues model that is prevalent across the space - even when tightly moderated, and corralled into projects and milestones there is never a cohesive view of -what the software should do-
And when it comes to all of the things I really care about when building or reviewing software "what should the software be doing" is really the core question.