Today there is no good way to show the delivery of requirements for one feature spanning multiple releases. For instance, if you have 3 of 4 feature requirements being delivered in Release X, but the feature itself won't be delivered until Release Y because of that final requirement, there's no good way to show this in Aha!. You simply have to move over the entire feature card or break the feature into 2 separate cards.
Thank you for your idea. Since this idea was created we introduced the concept of master features -- which would be a good option in the use case described here. Master features were designed to group features that will be delivered across multiple releases.
Given the availability of master features and historical support for this idea, we are unlikely to allow requirements to be assigned across multiple releases. We hope you can understand.
I should specify that I would like to be able to see this better in the Feature Board view.