Who would benefit? |
All users utilizing epics, features, and workflow syncing |
What impact would it make? |
|
How should it work? |
Currently when a feature status change causes an epic's status to change due to workflow syncing, the epic history does not include a reference to the feature status change so it looks like the user updated the epic status. This is not the way it works for features and requirements. If a requirement status is updated and causes the feature status to change, the requirement status change is noted in the feature history. |