Bug elements

As a professional, a little bit ,bug It has always been , But how can we make development quickly understand , Don't ask me ？

The problem description should be clear

bug elements ：

1、bug The title of the , A good title , It can let developers see the problem at a glance .

2、bug Project , Some companies have fewer people , May be responsible for multiple projects at the same time .

3、bug Which module does it belong to , Write down which module allows developers to quickly locate code blocks

4、bug Dealing with people , Who is responsible for repairing

5、bug Follow up person , Who will follow up after development and repair

6、bug The severity level of , The seriousness of the problem ,1 2 3 level

7、bug The priority of the , Online feedback questions , The test environment affects the test progress , Priority repair

8、bug The steps to reproduce , How does this problem recur

9、bug Screenshots and descriptions of the results , Stick the picture , Shut up developer

10、bug The expected result of , Since you think it is bug, Then write the expected results , Generally on demand
————————————————
Copyright notice ： This paper is about CSDN Blogger 「 Lack of balance , Please top up 」 The original article of , follow CC 4.0 BY-SA Copyright agreement , For reprint, please attach the original source link and this statement .
Link to the original text ：https://blog.csdn.net/gznc865958/article/details/120388408