{"version":"2.1.223","anchor":"bug-reports-from-cloud-workspaces-are-scoped-to-the-session","canonical_anchor":"bug-reports-from-cloud-workspaces-are-scoped-to-the-session","heading":"Bug reports from cloud workspaces are scoped to the session","tier":"notice","area":"Feedback","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/bug-reports-from-cloud-workspaces-are-scoped-to-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Bug reports from cloud workspaces are scoped to the session\n\nBug reports filed from a cloud workspace always attach that session's details.\n\n**What**\n\nFiling a bug report from a remote workspace always attaches the session rather than whatever scope was selected.\n\n**Details**\n\n- The payload's `scope` is forced to \"session\" when the report originates in a remote workspace, regardless of the chosen scope.\n- `remoteWorkspace: !0` and `remoteSessionId` fields are attached to the payload.\n\n**Evidence**\n\n`scope: l.remoteWorkspace ? \"session\" : n,`\n\n- Area: Feedback\n- Names: `\/bug`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}