Idea - Improve 'Find Usages' behavior when multiple Service Studio instances are open

Improve 'Find Usages' behavior when multiple Service Studio instances are open

New

Service Studio

I have two instances of Service Studio open, each connected to a different environment. When I do a 'Find Usages' on an element from Module A that is used in Module B (where Module B is only open in the other instance/environment), it points me to that other instance and it doesn't bring that Service Studio instance into focus.
My idea is that Service Studio should open the module in the current instance instead, especially when the environments are different.

7 days ago

Max França da Paz

Smart 'Find Usages' focus and Environment Awareness

The Problem: > When working with multiple environments (e.g., Development and QA), 'Find Usages' can be misleading. If I trigger it in Instance A, but the consumer is open in Instance B (connected to a different environment), Service Studio points to the other instance but doesn't bring it to focus. Even worse, it might lead me to check a version of the code that belongs to a completely different lifecycle stage.

The Proposal: > 1. Environment Validation: Service Studio should first check if the consumer module exists in the current environment. If it does, it should open it in the current instance. 2. Auto-Focus: If Service Studio decides to switch to another open instance, it must bring that window to the front (OS Focus). 3. Context Warning: If the "usage" found is in a different environment than the one I'm currently working on, a small warning or icon should indicate: "This usage refers to Environment X".

7 days ago