Problem Task associated with multiple projects

[Amanda37]

I have a situation with a customer where they are requesting that multiple problem tasks are associated with the same problem.

I have told them this is not best practice.  I have explained that the Problem is the Parent, and the PTASK(s) the child of said parent and that a PTASK can not have multiple parents in the same way that a change can not.

They are insistent they did this in a previous job via a related list.  With workflow that the parent would not close if any tasks are outstanding for the problem.

They give me this scenario:

Problem1 - Server issues occurring (PTASK1 - Replace specific server - SERVER TEAM)

Problem 2 - Another application but similar route cause (PTASK1 - Replace specific server - SERVER TEAM)

They do not want 2 PTASKs for the same server to be replaced. 

They want to associate PTASK1 with Problem2 as well.

Please can someone provide guidance on whether this has been done before?  
Is this a valid scenario or should they be doing something different at a parent level

Thanks

[Dr Atul G- LNG]

Hi @Amanda37 

Greetings!!

I can understand your situation and its tricky to handle this.

Fundamentally, 2 prb raised for 2 different issue/ reason and at time of RCA the cause is same, so In this case may be you can close 1 problem record , marked as duplicate and club it with the 2nd one, in relates list. 

This is only point i can think.

[Amanda37]

Thanks @Dr Atul G- LNG 

I will propose this to them as a suggestion - but will see if anyone else responds where they have actually done that (and associated the PTask to multiple Problems). I know it is not best practice but they are keen to explore it.

[Dr Atul G- LNG]

Sure @Amanda37 

Let's wait for other's input too.