Not that I know of. Another manual way is to Flag such defects providing corresponding defect nos. and mentioning a note about the same. But to your point this won't be enforced to the user and they will be able to close the defect irrespective of this dependancy.
Actually... It can be done... But it's going to require a field containing the id of the defect you want the dependency for. And, you're going to need to write some workflow code around the field change event of Status. Basically have the workflow look at the defect in the new field mentioned above... if that defect's status is closed, then you can close the defect you're looking at...if not...not.
Have fun playing with this.... [img]/images/graemlins/smile.gif[/img]
Senior Consultant, Orasi Software
Actually.. With QC9, you do not need that extra field to get the list of defects / requirements / runs / steps / tests / test sets / tests in tets set that are linked to a known defect. You'd use the new BugLinkFactory property of the Bug object, build a list from it, parse the list and check the properties of the linked objects. Then, you can deny users to change the defect status based on the values you found. You'd add that process in the Bug_FieldCanChnage event of the workflow when the changing field name is BG_STATUS.