How to Create a Form in Slack for Indicator Bug Reports

To create a form in Slack, build the form in a form builder, then post each submission into a channel through an incoming webhook. For an indicator community, the form should capture symbol, timeframe, chart type and alert settings so a repaint or alert bug can be reproduced without a thread of follow-up questions.

Build your bug report form free

Why a thread is a poor bug report

If you run a Slack community for an indicator or strategy, you know the usual report: "your alert didn't fire yesterday." Before anyone can look at it, you need to know which script and version, which symbol, which timeframe, what chart type, how the alert was set up, and when it happened. Each question costs a round trip, and half the users never reply.

Repaint reports are worse. Whether signal moved depends on the symbol, the timeframe, the chart type (Heikin Ashi and Renko change what a bar means), and whether the alret fires once per bar or once per bar close. Without those, you are guessing.

A form fixes this by asking everything once, in a fixed order, and postig a clean summary into a channel your support people already watch. The conversation in Slack then starts from a reproducible case.

What the form needs to capture

Keep it short enough that people finish it, but do not drop the fields that make a case reproducible. This is the set we use as a starting point for indicator support.

The alert fields only matter for alert problems, so hide them otherwise. In Qwenvo that is a conditional logic rule on the issue type question: show the alert condition and message text only when the answer is "alert not firing" or "duplicate alerts." Users reporting a plain display bug never see them.

Step by step setup

1. Create the form. Start from the bug report template, or describe the form to the AI builder on the empty-form screen and edit the result. You can also paste a Markdown outline (# title, ## per question, a [type] line, - for options) into the importer if you already have your questions written down.
2. Add the fields above. Type / to insert each block. Use dropdowns for script, timeframe and chart type so answers stay consistent and you can filter later. Make symbol, timeframe, version and issue type required.
3. Add hidden fields. Put the script name and version in the link you share, so a user clicking "Report a bug" from your release post arrives with those values already filled in. The hidden fields help article covers the setup. This removes the most common wrong answer, a version number typed from memory.
4. Allow large uploads. Screen recordings of an alert misfiring are the most useful attachment you will get. Qwenvo file upload accepts files up to 1 GB each.
5. Turn on partial submissions. In the form Settings, enable partial submissions. People who start a report and quit when they reach the alert fields still leave you their symbol and timeframe, shown as incomplete rows.
6. Create the Slack webhook. In Slack, create an app, enable Incoming Webhooks, add a webhook to your support channel, and copy the URL. Treat the URL as a secret, since anyone holding it can post to that channel.
7. Connect the form. Open the AI triage section in the form Settings and add a routing rule that sends to your Slack incoming webhook. Details are in the next section.
8. Share it. Pin the link in your support channel, put it in your Slack channel description, and consider a custom domain such as report.yourstudio.com so the link looks like yours. Our custom domain guide walks through the CNAME and TXT records.
9. Submit a test report with a deliberately bad case and confirm it lands in the right channel with the fields readable.

Routing reports into Slack

Qwenvo is a free form builder that our team builds, and AI triage with routing is one of the pieces that suits this job. Every submission gets a category, a priority (low, normal, high or urgent), a sentiment, a short summary and a suggested reply. Routing rules match on priority or category and send to up to five email addresses or a Slack incoming webhook.

A routing map that works for an indicator vendor:

Rules and categories are things you tune after you see real reports. Start with the table, then adjust once you see how submissions get categorized.

If you want every raw submission instead of triage-based routing, Qwenvo can also send a webhook to any URL. Slack's incoming webhooks expect a JSON body with a text field, so a raw form payload has to be reshaped first. A Zapier, Make or n8n scenario with a webhook trigger does that in a few minutes. The message you are aiming for looks like this:

{
  "text": "*Repaint report: Trend Ribbon v2.3*\n*Symbol:* BINANCE:BTCUSDT\n*Timeframe:* 15m | *Chart:* Heikin Ashi\n*Alert:* Once per bar close\n*Seen at:* 2026-11-03 14:45 UTC\n*Summary:* Long signal disappeared after the bar closed.\n*Screenshot:* https://example.com/upload/abc123"
}

Open the free bug report template

Where this sits in a Pine Script build

On the Pine Script indicator and strategy builds we deliver, the report form is the intake step of the support loop. The indicator ships with repaint-safe logic and alert conditions, and the form is how a user tells you when real-world behavior differs from the backtest. We wire the hidden version field to the release you shipped, so every report is tied to a specific build, and the reproduction fields mirror the inputs of the script itself.

For vendors who also run invite-only access, the same pattern applies: the form is where a customer says what broke, and the Slack channel is where you answer. The form does not replace the conversation. It makes sure the first message in the thread already has the data.

For the field-by-field details of a generic bug report, see our bug report form template guide.

Failure cases to plan for

• The webhook URL leaks. Anyone with it can post into your channel. Rotate it in Slack if it ends up in a public place, then update the form settings.
• Users pick the wrong issue type. Offer an "I'm not sure" option and let the summary from triage do the sorting, instead of forcing a guess.
• Alert settings are described from memory. Ask for the alert message text pasted in full. It reveals the trigger setting and any payload placeholders.
• Timezone confusion. Ask for the timezone with the time, or ask for the bar's date and the chart timezone shown on TradingView.
• Duplicate reports from one incident. Watch for a spike in one category. When ten reports arrive in an hour for the same script version, you have an incident, not ten bugs.

One honest limitation: Qwenvo does not have a one-click Slack app connection yet (it is being rolled out), so today you paste an incoming webhook URL. If your team wants to type a command inside Slack and have a form pop up there, that is a different setup from the one described here.

For comparison, Tally's free plan limits uploads to 10 MB per file, which is tight for screen recordings, and its custom domain and branding removal sit on the $29/month Pro plan. Qwenvo gives webhooks, AI triage wtih routing, partial submissions, a custom domain, badge removal and custom design for $0. Tally has been around since 2021 and has a large community, while Qwenvo launched in October 2026 and has few reviews so far.

What to measure

After a few weeks, check three numbers in the Submissions table and Insights: the share of reports with a screenshot, the share that arrive with a version number, and how many reports needed a follow-up question before you could reproduce the bug. If the third number stays high, a field is missing or badly worded. Drop-off analytics will show which question makes people quit.

Questions teams ask

Can I put the form inside Slack itself?

You can pin the link in a channel, add it to the channel description, or share it as a bookmark in the chanbel header. The form opens in the browser, and the submission posts back into Slack through the webhook.

Do I need a paid Slack plan?

Incoming webhooks are a Slack app feature, so check your workspace's current plan limits in Slack before you build. The form side has no cost on Qwenvo.

Can users submit anonymously?

Yes, as long as you leave the email field optional or remove it. Expect fewer follow-up answers, though, because you cannot ask for the missing detail.

Does this work for strategy backtest discrepancies too?

Yes. Add a dropdown option for "backtest differs from live," and ask for the strategy's input settings, the date range and the broker emulator settings the user ran it with.

Next step

Open the bug report template, add the symbol, timeframe, chart type and alert fields from the table, create your Slack incoming webhook, and submit one deliberately broken test report.

Build your bug form free