How to propose improvements in current bug tracking process?

Question

Welcome to SO @RON12345!

This is a big question that you have asked here, so let me see if I can break it up into manageable chunks (flagrantly stolen from your original post, no less!):

Inconsistency in raising bugs - What exactly do you mean by this? In my mind's eye I presume you mean that some bugs aren't being written/brought up? If that is the case, that can be gotten around by using a simple axiom (that I use myself) - "If you have to ask, 'Is this a bug?', then most likely, it is. It's a mental paradigm-shift for most testers to realize that all a bug is, is a record of something that went awry or could be improved.

Inconsistency in logging bugs - For something like this, I use a very simple and formulaic approach:

<Brief bug description>

1. Repro
2. Steps
3. Go
4. Here

ACTUAL:  This is what is actually happening.

EXPECTED:  This is what the expected behavior is supposed to be.  (As an aside, try to avoid using words like 'should' here).

<This is where you make note of any attachments that go along with the bug.>

We break our bugs down to the component in which it was found, the sprint it was found and note which team would need to make the fix.

Inconsistency in bug resolution - We use the following at my current job for resolution status:

Active - This bug is new, and has not been reviewed by anyone.

In progress - A developer has moved the bug into their queue and is now reviewing it.

Resolved - This bug has been fixed and re-assigned to the person who reported it.

As designed - This may look like a bug but, will be resolved by code changes or does not actually require a fix because of other factors like updates to the design by other teams.

Cannot reproduce - The developer was unable to reproduce the issue, and the bug may need more information or better repro steps.

Closed - I don't think this needs explanation :)

Difficult to apply filters due to less filters and meaningful values - This problem can be easily solved by creating more effective filters within TFS by which to search on. If you are an agile shop, consider adding a field that allows you to filter by sprint, for example.

Bug Reports are virtually impossible to create due to lack of training with TFS - I found this article on creating reports in TFS.

Best of luck to you and your project team/and I hope this answer is useful to you!