Issue tracking the process of managing and maintains listing of issues, as needed by an organization.

learn more… | top users | synonyms (1)

72
votes
15answers
4k views

Should developers enter bugs into the bug tracking system?

While developing (either features or bug fixes) I sometimes happen to discover bugs that are not directly related to what I'm working on. What should I do in that situation. Just fix it? Try to ...
56
votes
5answers
5k views

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. So ...
19
votes
6answers
701 views

What do you do with a heisenbug? [duplicate]

I've gotten a bug report from one of my users in a section of the software. The scenario is basically a databinding scenario where the user enters info, and that info is printed to pdf. The problem ...
50
votes
6answers
30k views

How to manage github issues for (priority, etc)? [closed]

I'm new to github, and am looking for advice on how to manage issues. I'm used to having priority and other ordering options but see that none exist. How do others manages issues during the ...
52
votes
5answers
3k views

Bug reopen vs. new

A bug was opened, fixed, verified and closed. A month later, it showed up again in a subsequent version after several iterations without any regression. Provided the bug characteristics are the same, ...
8
votes
5answers
413 views

Solving which bugs will give greatest cost benefit [closed]

I wanted to get an idea of categorizing bugs based on how easy is it to solve and how much benefit it will give me. for e.g., if there is a bug which will take say an hour (double file close etc.) to ...
26
votes
9answers
1k views

Should I log trivial fixes?

I'm in a code shop of two. And while I understand that a bug tracker is useful where the number of programmers is greater or equal to one, I'm not so convinced that logging bugs, changes, and fixes is ...
20
votes
4answers
3k views

How to close a bug that is no longer relevant

I'm currently on a medium-sized team of web developers. We're using jira for bug tracking. We're working on a product with frequent layout changes. A lot of times bugs are filed about a bug in the ...
15
votes
7answers
744 views

Bug once in a while, but high priority

I am working on a CNC (computer numerical control) project which cuts shapes into metal with help of laser. Now my problem is once in a while (1-2 times in 20 odd days) the cutting goes wrong or not ...
111
votes
17answers
6k views

Should I tell someone that their commit caused a regression?

When you track down and fix a regression—i.e. a bug that caused previously working code to stop working—version control makes it entirely possible to look up who committed the change that broke it. ...
7
votes
9answers
2k views

Setting Up a Development Environment

I am part of an organization that is formalizing their software development processes/capabilities/etc. While the organization is not traditionally a software organization, they want to do this right ...
27
votes
6answers
985 views

Why could citing bug IDs in patch notes be considered a bad practice?

Based on a comment and subsequent upvotes from Bug reopen vs. new: Citing bug IDs in patch notes is just.. very unfriendly. – Krelp It appears at least some people feel that referencing bug IDs ...
17
votes
7answers
595 views

Herding your users to your bugtracker

I have a fully configured mantis bug tracker for tracking issues in apps that I create. When an user is disciplined and goes straight to mantis to write a issue report, he/she will have fastest ...
7
votes
5answers
742 views

should you always enter a bug in a bug tracking system [duplicate]

Possible Duplicate: Should developers enter bugs into the bug tracking system? Should I log trivial fixes? For a project I'll be doing in school soon I will be working with 6 other people. ...
5
votes
6answers
8k views

In agile environment, how is bug tracking and iteration tracking consolidated.

This topic stemmed from my other question about management-imposed waterfall-like schedule. From the responses in the other thread, I gathered this much about what is generally advised: Each story ...
12
votes
4answers
6k views

How to classify bug severity to complement our priority classification?

At my current job we have Low, Medium, High priority bugs. Low priority bugs are small errors that don't stop shipping or cause real trouble for any user. Medium priority bugs cause some internal ...
9
votes
4answers
554 views

Is reference to bug/issue in commit message considered good practice?

I'm working on a project where we have the source control set up to automatically write notes in the bug tracker. We simply write the bug issue ID in the commit message and the commit message is added ...
5
votes
3answers
147 views

What is a better design for exposing information in a bug tracking system?

We're working on a BugTracking system and are still in the learning process. A BugReport has a title, description, (...) and also a tag. A tag represents the progess of the BugReport, e.g. New : ...
3
votes
2answers
220 views

Feature code + infrastructure code - how to structure the commits / JIRA issues?

Say that you work on a feature described by a single JIRA ticket and during the work, you: Create feature-specific code like the GUI or specific use-case behavior. Some of the code was generic so ...