ticket dependencies? Example use-cases or scenarios that you're thinking of for this feature would probably help the devs and others understand what you're looking for...

Important Note:
While this could have been lumped into CHD-736 which deals with merging tickets based on a slave/master context. It has been suggested in the corresponding forum thread that this could potentially serve as the foundation or starting point for developing a revised merget ticket solution.

I tend to agree with these sentiments, but more importantly this should be an independent request based on the fact that is a more generic (or abstract) merge ticket feature. To me it seems like even if we don't choose to implement a more robust merge ticket system based on slave/master for example, we could still implement this to satisfy a select group of users.

^^^ Above comment is referring to CHD-911 (in case of confusion)

Tentative +1 vote from the forums.

http://www.cerb4.com/forums/showpost.php?p=14363&postcount=10