This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1092 As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release.
In the mapping:
Feature -> User Story
If you create a new user story in a fixVersion that's linked to an Aha! release, Aha! reflects a new feature. If you move a user story from one linked fixVersion to another linked fixVersion it is not changed in Aha!
In the case where a development team determines they cannot finish a user story and need to move it out, this is problematic. When the Product manager ships that release, the unfinished features will be moved to another release of their choosing. It can cause confusion when the user stories they agreed belonged in a different fixVersion suddenly show up in another fixVersion (or on their Sprint board).