Modern software systems are increasingly built as component-based architectures, e.g., as microservices. However, such architectural styles result in many challenges for development teams regarding issue management: Since the individual components are developed independently of each other, the teams manage the issues of the respective components often in separate issue management systems, making the tracking of cross-component issues much more difficult, i.e. issues that affect multiple components concurrently. To solve this problem, in previous work, we developed Gropius, which is a tool that acts as a wrapper for existing issue management systems enabling the management of issues across the different components managed in different issue management systems. While Gropius is particularly suitable for stakeholders who want to have an overall view of the architecture and the issues therein, a developer’s daily work is primarily done in an IDE. Thus, frequent context switches between the issue management systems and the IDE reduce developer productivity, so IDE plugins for issue management have been developed in the past. However, these do not support cross-component issue management features as provided by Gropius. Therefore, in this work, we present Gropius-VSC, a Visual Studio Code extension that allows developers to manage cross-component issues directly in Visual Studio Code.