Currently when a release is re-ranked in Aha, only the items that are moved have the rank updated which leads to multiple rank fields in the engineering system to have the same value; or constantly resending all release fields to send the new stack rank. This leads to having to manually rank/order a release in both systems to match so iterations can be properly built in Azure.
Thank you for your idea. This was designed to work this way intentionally to avoid causing issues in customers' development systems. Every time a feature is moved in Aha! we update the rank of all features in the release. We do not send updates for every record because doing so would create floods of traffic on customers' servers and would be likely to cause them performance problems.
Given the explanation above and the ability to resend all features by resending the release, we are unlikely to make updates here. We hope you can understand.