See PHI251. This requests an "Ignore generated changes." option for Owners. There may not be a direct path to this today, but this is almost certainly a plannable feature.
See PHI285. An install would like a way to monitor changes to Herald rules. This mostly needs planning. The actual implementation may not be difficult, it's just not clear if "Herald rules for Herald rules" are the best approach.
See PHI592. A diff with 600MB of videos required more than two hours to turn into an email patch, which exceeded the task lease duration and cascaded into various other kinds of problems. This is somewhat adjacent to T11767.
See PHI580. An install would like write API access to object relationships (depends on, fixes, etc). This is complicated, but perhaps plannable, and we may be able to put a reasonable facade with partial support into the upstream.
See PHI483. The available actions from "Changes Planned + Draft" (and maybe "Abandoned + Draft") are currently too permissive. Fewer actions should be available; particularly, "Accept" should not be available and the actions should generally be more similar to the actions available from "Draft".