Skip to main content

Questions tagged [issue-tracking]

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

33 votes
12 answers
8k views

It's obvious why you should track ongoing bugs. It's not at all obvious to me why you should track solved bugs. If a bug is solved, then just email the person who submitted it, delete the bug once ...
J. Mini's user avatar
  • 1,025
2 votes
3 answers
440 views

If you solve a bug in a poor way, it might result in even more bugs in the future, so I need a way to validate if the fix was actually good. Time between the bug assignment and issue closed doesn't ...
ayowhatthedogdoin's user avatar
1 vote
1 answer
143 views

The idea is that if an app I like periodically has noticeable bugs or issues, and it’s commercial, not open source (in this case, AirBNB, but I feel this way often towards many apps), I would like to ...
Julius Hamilton's user avatar
55 votes
14 answers
8k views

Our company have a support team and a dev team. We require reproduction steps on every bug report, however sometimes the support team submit reports without and become frustrated when dev close them ...
Chris's user avatar
  • 535
2 votes
3 answers
740 views

Whenever I do temporary fix I want it to really be temporary. However, there is no way to come back to it later, as the fix might be a part of a bigger issue. Let's imagine that we have for some ...
Random Guy's user avatar
0 votes
2 answers
238 views

I'm starting to define how issues should be handled in GitLab. Most specifically whether the author should be editing the original issue to keep it up to date or use only comments. Let's say that you ...
cuoka's user avatar
  • 119
-3 votes
1 answer
692 views

I'm starting to write production software (just for myself, not for a company with a pre-set mode of operations for this). I want to find a way to send a message from my users to me (the developer) ...
CyanCoding's user avatar
3 votes
5 answers
1k views

Our software user interface was originally written in another language. Some of the English translations are poor. When I raised one of these as a bug, the manager got angry with something like "...
AlainD's user avatar
  • 150
0 votes
2 answers
267 views

I'm working on a certain group repository. This repo has an issue tracker, but - it's not intended for all issues, and certainly ot for our day-to-day development work. The point is - I need to track ...
einpoklum's user avatar
  • 2,828
0 votes
2 answers
255 views

How do "you" handle runtime incidents (say, a null-pointer exception, or an API input data validation failure) so that you (a) don't miss any, and (b) aren't spammed by duplicates? Are you doing log ...
KlaymenDK's user avatar
  • 447
2 votes
3 answers
859 views

Sometimes, on an IT helpdesk, you have tickets with a few shared characteristics. They're low priority--just minor annoyances to user They're extremely hard to reproduce for testing You've exhausted ...
user11633140's user avatar
1 vote
0 answers
135 views

In GitLab, an issue is usually closed once a Merge Request is approved and merged into master. However, what should happen with issues that are closed because of other reasons? There could be ...
Thomas Kainrad's user avatar
6 votes
3 answers
1k views

I often encouter the following pattern: A bug is resolved/closed as duplicate of another still open/unfixed bug. I have trouble understanding the reasoning behind this strategy. From my naive point ...
ead's user avatar
  • 181
13 votes
3 answers
5k views

We have a bug process that is currently being worked. We have 3 levels of bug: P1 bug: Bugs that prevents users from working. They must be solved on the spot. P2 bug: Bugs that are impacting but ...
Andy K's user avatar
  • 285
2 votes
3 answers
272 views

My question comes from using the agile template in Azure DevOps though its more of a general question about dealing with bug work items. When a bug work item has been investigated and the issue has ...
mhep's user avatar
  • 245

15 30 50 per page
1
2 3 4 5
11