What are the strategies behind closing unresolved issues in different issue tracking process definitions

Posted by wonko realtime on Stack Overflow See other posts from Stack Overflow or by wonko realtime
Published on 2012-10-30T16:58:32Z Indexed on 2012/10/30 17:00 UTC
Read the original article Hit count: 234

Recently, i found out that it seems to me like a good part of the "administratives" tend to close "issues" in their bug- and issue-tracking systems with the reason that they don't fit in "their next release". One example for that can be found here: https://connect.microsoft.com/VisualStudio/feedback/details/640440/c-projects-add-option-to-remove-unused-references

Because i fear that i've got a fundamental lack of understanding for this approach, i'm wondering if someone can point me to informations which could give some insight in the rationales behind such processes.

© Stack Overflow or respective owner

Related posts about bug-tracking

Related posts about issue-tracking