app-scope-resolution

Service identification uses the extracted app-id to map directly to application components within documentation catalogs. This cross-referencing mechanism pinpoints the relevant services, screens, and entities affected by an issue, enabling precise scope determination for automated workflows.

To identify affected application components from issue comments, parse the text for embedded app-id identifiers and map them to a catalog file. This isolates the specific screens and entities related to the issue, streamlining targeted updates and validations across multiple app projects.

The app-id scope resolution mechanism works by parsing issue bodies and HTML comments to retrieve specific app-id identifiers. It then cross-references these identifiers with catalog files to map them to the relevant application services and entities for workflow execution.

To map an app-id to related services, first ensure your issue description contains the app-id embedded within an HTML comment. Running the scope resolution process then automatically parses this identifier and cross-references it against your catalog files to output the mapped services and entities.

For service mapping to work, the app-id must be embedded in the issue description as an HTML comment formatted specifically as <!-- app-id: XXX -->. This precise syntax allows the parser to successfully extract the identifier and map it to the application catalog.