I work in a development store that uses legacy software bug tracking. They are currently weighing alternatives to replace it.
This software tracks our errors as well as tasks for new feature requests.
We create the main application that we configure and support for various clients. In this vein, we have customer service specialists who assist both with errors in the main application and with errors in the client configuration.
Due to this bias in customer service / technical support, the proposed alternative is Microsoft Dynamics CRM. I have no experience with this, but from what I can say, it meant more to track customer problems than to track errors and quality control from a development point of view.
Has anyone used Microsoft Dynamics CRM and found it to be a suitable error tracking software?
I am having trouble recognizing the benefits of using CRM software to track errors / tasks. I could figure it out for sales, but I think having separate bug tracking software makes more sense than putting everything together. Does anyone else encounter such a predicament - what was the result and / or convincing arguments for or against this approach?
EDIT: clients do not need to add errors directly; they call our support team and we open a ticket. Our state-of-the-art software has been expanded to track problems and track errors / symptoms as an all-in-one system. Unfortunately, he does not cope very well with this - the gap occurs at the source control level. We cannot associate a set of changes with an error or task.
TFS / , Microsoft Dynamics CRM . , , , , #, , /QA/.
!