Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
We don't have someone in between but I tell project managers and QA that screenshots should show me the url at least.
I get the same tickets as you but I don't expect whoever is writting them to know which class has the bug. It's my job to investigate and fix.
As a developer, investigating bugs is your job. Don't expect someone to review the ticket then tell you where the bug is. Finding the cause of the bug is 50% of the fun.
I want to add this : if your Project manager or QA don't include reproduction steps then go have a face to face chat and ask them politely to add the steps to the ticket.
If the bug is random or doesn't always happen, then explain to them that it will take some time for you to be able to reliably reproduce it. Until then you can't comment on cause or time to fix.
Communication is key here.
here's what we do:
business unit's technical side is in charge of writing end-2-end and integration tests. if they find a bug, doesn't matter how, they edit our test suites on CI/CD server to show the bug.
in dev team then our builds turn automatically red showing exactly where the problem is, so we go down the rabbit hole, write eventually additional unit tests, write the code, commit, push and finger crossed till the build is green again
it's a pretty quick and non bureaucratic way to deal with these situations.
the biggest tradeoff is that it makes harder to extract good metrics for individual evaluation.
but if you are committed only to results and only as a whole team tho, this is not a problem (pretty hard to find this kind of management. lot of managers love to have someone to blame and someone to praise, it makes their job easier)
I, Can Ban, can ban Kanban.
Snob24365dIt's cs student interns here who test manually and write automated tests..
Documenting bugs precisely in Atlassian Jira is required here, else you get f**ked. The bug description quality is pretty good tbh.
Close. Reason: unable to reproduce
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job