issues service has conceptual issues related to pulls from other repos (BB-2403)
imagine you have:
- a master repo with master issue tracker for the sw project
- a forked repo with own issue tracker for the subproject that some developer is working on
at some time later, you decide that you want to pull the stuff from the developer's repo into the master repo.
This is very annoying, because you manually have to fix all those issues afterwards.
The only work around I can think of currently is to disable the issues service before pushing changesets you pulled from another repo using its own issue tracking with issues extension.