Where can I turn to if I can’t fix a bug?
I am looking for resources to turn to when I don’t have the answer for something. I lead a team of software developers. We have been rolling out new software releases on a monthly basis.
Why is it so hard to get employees to update the issue tracker?
I’ve always had this struggle to get folks to update their issues, both at my company and at work. I’ve had a few cases when people actually do it from the goodness of their heart, but ~70% of the time I have to be chasing people down.
Why do some big projects, like Git and Debian, only use a mailing list and not an issue tracker?
Bug tracker for any decent sized project seem like a bit of a no-brainer to me – it makes it really easy to organise hundreds or thousands issues, without issues colliding or getting mixed up.
Distributed Issue Tracking [closed]
Closed 9 years ago.
Issue tracking system by function/method
I often feel that it would be more convenient if, within an issue tracking system, each issue were attributed to a certain function/method. Then, we can easily list all the issues related to a certain function/method. Many issues can be clearly attributed to a certain function/method. At times, we may want to look at issues sorted by the posted/edited time or by importance, be many other times, we want to look through only the issues related to a certain function/method.
Solution with multiple projects and (GitHub) single issue tracker and repository
I have a Visual Studio solution with multiple projects:
Business issues in the issue tracker?
Most issue trackers are targeted towards developers. But when working in a small team that includes business people: does it makes sense for them to put non-dev issues inside the tracker?
Business issues in the issue tracker?
Most issue trackers are targeted towards developers. But when working in a small team that includes business people: does it makes sense for them to put non-dev issues inside the tracker?
Business issues in the issue tracker?
Most issue trackers are targeted towards developers. But when working in a small team that includes business people: does it makes sense for them to put non-dev issues inside the tracker?
Business issues in the issue tracker?
Most issue trackers are targeted towards developers. But when working in a small team that includes business people: does it makes sense for them to put non-dev issues inside the tracker?