Why this is needed: I use the feature board view a lot to discuss our new-feature plans with engineering. As and when we make decisions, features can move sideways (e.g., from a Parking lot to a named release) or up and down (e.g., in a single Parking Lot list). This would be in addition to other feature content changes we make, e.g., add a new requirements, tweak an existing one, etc. Right now, the notifications engineering receives are for very granular changes, i.e., each and every change for a feature is an email. Which forces them to parse emails to figure out the "net change" that has occurred since a certain time in the past. This quickly becomes very tedious and cumbersome when there is a lot of planning and feature content change activity.
Ideas to address the need: