You have to be very careful when asking a question of this nature, because it's very easy end up asking a dreaded shopping/recommendation question. You know, like this:
What is the best bug reporting tool to use for a game written in C#?
We don't do those types of questions on Stack Overflow. We are not a recommendation engine, and we won't abuse the Q&A system to build lists. Questions like that will end up closed as "off-topic" or "too broad".
Instead, you need to ask an actual question about accomplishing a particular goal (e.g., capturing and emailing bug reports from a C# application). Describe your specific requirements in detail, making sure to note any caveats, special considerations, and other limitations. Then ask how you can achieve this goal.
It would also be looked on approvingly if you included in the question some of the ideas that you've already had, and possibly some solutions that you've already investigated. People like to see that you've spent some time and invested some effort into solving your problem already. They're much more likely to help you if you show that you are willing to help yourself. More importantly, they're less likely to vote to close your question.
In the process of answering a question like this, people will inevitably make suggestions of third-party products. But that is okay, since there is a clear question being asked and answers can be objectively judged on whether they meet your stated criteria.
The truth is, you don't really care to see a list, summary, or comparison of all the different bug reporting tools that are out there. If you wanted that, you could just use Google. But that is just noise. You're looking for a specific solution to solve a specific problem. And that's what Q&A is for.
Related Reading: Q&A is Hard, Let’s Go Shopping!