"If you don't know enough, worry business email list more." If you are a newcomer who has just taken over the product, theoretically, the product-related information, those who develop and test the students, understand more and more profoundly than you. Before dealing with bugs, ensure that your cognition and the other party’s cognition are in agreement, and then start thinking about solutions, which can avoid some pitfalls. Secondly, after the plan is finalized, it is necessary to synchronize the relevant parties
It takes time to fully understand and be familiar with the requirement background (what is it? Why? Past, present, future) design purpose, business process, functional scope, relationship between related modules, etc. Before reaching a consensus, don't rush to a conclusion, spend more time on thinking and communication, otherwise your solution is likely to be inapplicable and there will be "bugs"
Finally, one more question, is your plan necessarily the best? Have you captured the essence of the need? Can it adapt to future flexible changes? Have you discussed with relevant parties? Don't work behind closed doors
2) How to deal with BUG problems
Obtain clear, complete and comprehensive bug descriptions from registered stakeholders (graphic video)
Determine whether there are related system configuration problems (such as the resignation status of employees in system A, which affects the normal operation of system B)