Report a Mockspace bug

Use this for problems with Mockspace itself: the site, the workbench, the viewer or the CLI. For a problem in a project you are reviewing, use that project's own bug report instead. It goes to that project's members, not to the Mockspace team.

Turn on the report button#

The button is off until you turn it on. It only changes what you see: anyone signed in can send a report either way.

1. Sign in, open Settings and find Developer.
2. Turn on Mockspace bug report button. The choice is saved to your account, so it applies in every browser you sign in with.
3. Report a Mockspace bug now floats at the bottom right of every page. In the workbench it sits at the bottom right of the canvas, above the canvas controls.

To hide it again, turn it off in the same place.

Send a report#

1. Select Report a Mockspace bug on the page where the problem happened. The report opens over the page, so you keep your place. It shows that page's path, for example /mockspace-web. It never includes the part of the address after ? or #, where links can carry tokens. Select Don’t include this page to leave the path out.
2. To add a screenshot, select Capture this page. Your browser asks what to share: choose this tab. The report hides itself while the picture is taken, and sharing stops as soon as it has the picture. On a phone, or in a browser that cannot capture, select Attach an image instead.
3. Mark the problem. With Highlight, drag on the screenshot to draw a box, or click two opposite corners. With Hide, cover anything private with a solid box. The cover is drawn into the image itself, so what is under it is never sent. Enlarge gives you more room; Undo, Clear marks, Retake and Remove screenshot take things back.
4. Describe what went wrong. A title, the steps to reproduce and the expected behavior are optional, but they make a fix quicker.
5. Choose the Impact: Minor, Major or Critical. Critical reports are picked up ahead of Minor and Major ones.
6. Select Submit report.

Nothing else is sent with it: no page content, console output or browser details, and no image unless you add one. A screenshot stays in Mockspace, where you and the Mockspace team can open it; the GitHub issue only links to it. If the team needs something else, paste it into the report yourself, without tokens or passwords.

If reporting is not set up on this service yet, you can still capture, mark and write your report, but Submit report stays off and says why.

If Mockspace does not answer, your report stays as it is. Select Retry report to send the same report again. A retry never creates a second report.

Closing the report with its close button or Esc keeps your draft while you stay on the page. Discard draft clears it.

What happens next#

• Your report becomes a request in the Mockspace team's own project. The team and its agents plan and fix it through their usual review.
• It is tracked as an issue in the Mockspace GitHub repository. The repository is internal to your organization, so members of the organization's GitHub can read the issue. The issue quotes your report and names you with your email, so the team can follow up.
• The confirmation shows the issue number, for example Tracked as issue #41. If the issue is still being created, the confirmation says so. Your report is saved either way.

If this service is connected to Slack, the report is also posted to the team's #mockspace-bugs channel. A reaction on that post shows where the report stands, from received to resolved, and progress updates arrive in its thread. The GitHub issue stays the tracking record.

Sending a report does not give you access to the Mockspace team's project. The issue is closed when the fix is merged, or when the team closes it on GitHub. If it is reopened, the report counts as unresolved again.

If you cannot report#

• Mockspace bug reporting is not set up on this service yet: this service has no connection to the Mockspace team's GitHub repository. This is normal for a local or self-hosted service.
• A workspace that runs without sign-in cannot take reports, because each report needs a signed-in account.