Context. In the development of component-based systems, often issues affect multiple components or must reference issues of a different component, resulting in the Cross-Component Issue Management System, Gropius being invented. Gropius needs to synchronize issues with traditional per-component Issue Management Systems (IMSs), e.g., GitHub or Jira, to have relations between issues on different IMS. Problem. The existing system can currently communicate exclusively with GitHub supporting only a limited subset of the required features. It is susceptible to duplicating issues and timeline items potentially infinite times due to missing identifying meta information. Objective. We provide a redesign of the Gropius Sync, designed to be modular and able to host multiple methods of duplicate detection. Method. We implement the new Sync Framework, adapters for GitHub and Jira as representatives for traditional IMSs and compare different methods for duplicate prevention. Result. We succeeded with our plans to provide a new Sync that can both sync to GitHub and Jira and thus demonstrate the feasibility of the sync. We successfully detect and prevent most previously found issue duplication loops. Conclusion. The new Gropius Sync allows synchronization between multiple IMS Projects without runaway duplication of issues.