3 ms·

Person reporting a bug often will not be having knowledge of the source code, right? So the best he/she can do is to assign the bug against a particular compone

• mariocesar 15y ago
  Yes! and No! I am using trac right now and this the sort of things I want to avoid, instead of over-describing all my tickets, I would like to have an smart/programmable middleware that can notify users using some logic. An example, someone create a ticket and later commit this with Git: rev 1 "Workaround for fixing Z stuff, as last X library update breaks the code. fixes #1001" I would really like to have the power to catch this event and inspect the manifest of the commit and if this is fixing a ticket for a part of the code I am aware other writers had been made changes, and send notifications to them, or even better change the ticket to status to "waiting approval" to the first author of that part of the code. It's not about making notifications, or adding more describers to tickets, it's about let me "teach" the bug tracker how to behave on a certain case. I will 100% use some bug tracker that let me easily hack him to do that.