This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-14573 Manual Sending of Requirements to integrated development tool.
We have a complex portfolio of many products and many GitHub repositories. Often, we will want to break up the feature into requirements and send them to different repositories where different teams can work with them. However once a feature is integrated to an issue in one repository, all of the requirements (and any subsequent requirements) are automatically sent to the same repository even if we want to send them elsewhere to be worked on. It leaves confusing orphaned issues in the old repository and doesn't make sense.
If you could choose whether to send them or even better choose a different repository, similar to the sending through of a feature initially this would be ideal. The "Approve all outgoing changes" choice would slow down business too much this is not an option for us, we just want to stop orphaned issues and improve our cross-tribe collaboration using Aha!