How do you handle related bugs in Bugzilla?

Question

In our environment, we have a basic code base and several client-specific implementations of this code base. When a client raises a problem, we need to determine if this is a particular client’s problem or whether it is a major code problem.

We use bugzilla to track our errors, and we have a bugzilla product for the main code base, as well as for the implementation of the client (because they configured the offer for extended functionality). When a client raises an error related to the main code base, we need to raise this error in two bugzilla products - the kernel and the client, so that both teams are aware of this problem. Ideally, we would link these errors together so that we do not spend efforts trying to fix it twice, and that 2 Project Managers are fully informed about the progress of this problem.

My best idea so far is to use a comment / description, including the work “Refers to Error”, since it seems that the word error magically becomes a link to the specified error, which makes it easy to get to this other error detail. This can then be found using the criteria "Comment contains search criteria."

How do others do it?

Answer 1

I would use the depend / blocks fields if they are included in your Bugzilla, with the following workflow, approximately:

• An X error was reported in the client product.
• , , "" ( Y), (Y- X, X Y);
• Y;
• ​​ , ​​ X ( ).

depend/blocks :

• : - Y, , X, ;
• : Bugzilla , , Y X.

, . , . , , , . , , depend/blocks.