Hello everyone! I have been reading some threads/articles online but I would deeply appreciate some feedback based on my particular case. The context: a complex sector, historically no QA, large and old legacy codebase + new code based on microservices. Not using Scrum in the intended way, only so…

Always add all new bugs to the current or next sprint even if they are in the legacy code, minor, non-priority, etc (if you believe they have to be fixed), then devs or stakeholders move them somewhere else but they will see them Use a labeling system, create tech debt backlog, and create dashboard…

You can create an automated check that exposes the bug. And, instead of invalidating the build, it sends an email/message to the developer about the possible problem. This way people will be continuously warned about the issue. Continuous, explicit, and specific alerting.

While I like the idea… It’s too easy to ignore emails or to setup a rule to automatically delete certain mails.

Hi Welcome to the most awesome software quality community on earth @hellendd . My opinion only, but unless you can get agreement to fix a bug before the next release, you are better off forgetting about and closing it. Adding a bug to yet another reminder list is like having 2 backlogs, and ultima…

Besides the tester, the others don’t care about any of the discarded issues. The business isn’t affected by them according to the Product manager and the team. So why spend all this extra effort? I’ve worked in a place where we did what you mentioned for open backlog issues. For about 3 weeks eve…

Doing that for rejected issues is a nice way to destroy your relationships with many people and the automation completely ignored from then on. In my experience at some point with failing automation, all the other persons would say: that only the testers should receive this report. We only care abo…

How to track legacy (or non-priority) bugs if not in the product backlog? As long as you do your job of informing the product manager of the issues noticed and do the bug advocacy as you see fit, you can move on. It’s their job to add them to the sprint, backlog or ignore.

I agree with you and basically, it was one of my points (7) :slight_smile: I just provided different options because situations might be different and people may have different reasons and motivations. I’ve been in situations as you described and I’ve worked for a big corporation on a project with a…

Thank you @shad0wpuppet and @ipstefan ! @ipstefan so, were you mostly reporting fewer new issues or rejecting more already opened issues? or a balanced combination of both? Indeed, I would not like to invest my (and others’) time in something that is not valuable to customers. At the same time I am…

How to track legacy (or non-priority) bugs if not in the product backlog?

Discussions

conrad.braam (conrad) 18 April 2024 13:46 9

Yep, basically like this thread Severity vs Priority vs Urgency vs Impact of Software Bugs - #4 by steve.green

Topic		Replies	Views
Bug Backlogs/Mountains, how do you deal with them? Archive	16	2084	4 August 2021
Bug trackers in agile, are they really necessary? Archive tools	10	2183	12 June 2017
How do you prioritise bugs? Archive	35	2310	26 July 2021
Scrum Teams Without Developers - Is It Worth Logging Bugs As Backlog Items? Discussions learning , agile	14	245	29 July 2024
What are the many ways you categorise bugs? Discussions communication , collaboration , bugs , test-reporting , bug-reporting	8	251	10 January 2025

How to track legacy (or non-priority) bugs if not in the product backlog?

Related topics