Custom workflows

Capture supports multiple ways to organise your bug reports depending on the context. Use spaces and capture keys to create custom workflows for different teams, projects, or types of issues.

Organizing with spaces

Spaces help you keep your Capture dashboard organized by grouping related bug reports together. You can create spaces directly from your Capture dashboard - for example, one space for customer-reported bugs, another for internal QA, and another for a specific product feature.

Custom workflows with capture keys

Each space has its own capture key, which you can use to configure custom destination settings and automation. When someone creates a bug report using a specific capture key, it automatically uses the configured settings for that key.

This enables workflows like:

Customer bug reports - Create a space for customer issues that automatically sends a notification to your support channel whenever a customer reports a bug.

Project-specific tracking - Create a space for a new feature that automatically routes all bug reports to the correct project in your issue tracker, with the appropriate labels and priority already set.

Team-based routing - Create separate spaces for different departments within your organisation, each configured to notify the right team and create tickets in the right place.

Configuring capture key settings

To customize the settings for a space's capture key, go to that space in your dashboard and click settings. Here you can configure:

• Default destinationss (which integrations to publish too)
• Default project, labels, priority, or status for each integration

Once configured, any bug report created with that capture key will use these settings automatically.

Using capture keys

Web SDK

There are multiple ways to specify which capture key to use:

During initialization - Set the capture key when adding the SDK to your page:

<script>
  window.captureOptions = {
    captureKey: "YOUR_CAPTURE_KEY",
  };
</script>

On trigger elements - Attach different capture keys to specific buttons:

<button data-capture-trigger="CUSTOMER_SUPPORT_KEY">Report an issue</button>
<button data-capture-trigger="INTERNAL_QA_KEY">QA bug report</button>

In URLs - Perfect for requesting specific types of bug reports:

https://example.com/app?capture=YOUR_CAPTURE_KEY

Programmatically - Trigger the widget with a specific key from your code:

Capture.open({ captureKey: "YOUR_CAPTURE_KEY" });

Next steps

Ready to set up your first custom workflow? Start by creating a space in your Capture dashboard, then configure its capture key settings.

Want to send bug reports to Linear, Jira, Slack, or other tools? Check out Connecting integrations to enable automatic routing.