Hi Matthias,
1) Yes.. This is where we started and ran into issues when there is a hierarchy in place.
2) Yes... We had that at one point, and had mixed results.
3) We were trying to avoid all the complex code associated with this approach.
- If the "Contains/Contained by has changed", fire the script.
- In the script, find the old "Root Node" and the new "Root Node", the Document ID doesn't seem viable as the new and old value don't seem to be both available in a script.
- If if the "Root Node" is the same, do nothing. If the "Root Node" is different, then iterate over the delta issues and all of its childrent (children's children (.... for all levels)) and perform the logic we need performed.
All we need to do is to perform some reset logic when a requirement moves from one document to another. If we have to build #3, we can. A simpler, and less fragile approach is much more desirable.
-Sean