Yep, we went through and triaged all of the Connect bugs recently. I think we've said before, but we don't use Connect as our primary bug tracking database, so we need to go through and migrate as necessary. Our process for it is:
- Resolved External = We've migrated it to our database. That doesn't mean it will get fixed by the next release, but that it's a a bug or suggestion we're interested in looking at.
- Resolved Fixed = It's already fixed, either in a previous release or an upcoming release.
- Resolved As Designed = Thanks for the suggestion, but we feel it's working correctly. :)
I think those are the ones that are mostly interesting. I think we used to resolve some as Postponed, but we now resolve them as External if we want them and postpone them in our product database. (Postponed means it's too late to do anything about it. These are usually feature suggestions or lower priority bugs).
Thanks!