Bug: raise them fast or raise them with full information?Report
A bug with full information is always good. However, in many projects I had chances to work with dev team as internal and external tester. I have two kind of dev:
1. They like quick bug and no need full description, sometimes just image is enough. They love to fix it quick (sometimes no need to raise, just let them know what happens). Reading too many steps in bugs makes them sick
We all know that writing full description bugs with complex template takes us ton of time. Not good for quick run projects but good for tracking propose.
So which team should fix themselves for better process quality? What we should tell our boss to improve the team?