Bug tracking automation (from visitor message to closed task)

What bug tracking automation does in Bugfix

Each message from a visitor automatically becomes a task in the team's task system, TeamOps, inside the project of the site where the message was written. The assignee is taken from the directory “project → owner”, so a task never stays without an assignee. A notification goes to Telegram in parallel.

The original text of the message is kept. An AI prepares a clear task description next to it and does not replace the original.

How a message turns into a task

In Bugfix, bug tracking automation runs as one chain.

1. The visitor sends a message. At intake Bugfix applies its anti-spam rules: a hidden trap field, a limit per device and no more than one message every 15 seconds.
2. The original is saved, and the AI prepares the readable description of the task.
3. The message is checked for duplicates and for signs of urgency. Robots and test runs are marked separately.
4. A task appears in TeamOps in the project of the site, with an assignee from the directory, and a Telegram notification is sent.
5. When the task is closed, the message is marked as fixed and the author is told.

Duplicates, urgency and test runs

Bug tracking automation merges repeats by three rules:

• an exact repeat from another visitor is merged with the original message;
• the same person who adds the same problem again is merged by word stems;
• different visitors with similar text are merged by a match threshold.

Urgency comes from a narrow list of phrases such as “does not open”, “does not work”, “white screen”, “freezes” and “crashes”. A message that contains them gets a raised urgency in the task.

Robots and test runs are marked on their own and do not turn into live complaints, so a check of the pipeline does not fill the list with false reports.

Telling the author that the bug is fixed

The loop closes without a manual reply. When someone closes the task, the message is marked as fixed automatically, and its author sees “✅ Fixed in version N” with an explanation. Duplicates are closed together with the original.

The same note belongs to the replies of the team that the author reads on the “My requests” tab of the widget, next to the history of their own messages.

Where bug tracking automation helps

• Several sites, several owners. The directory “project → owner” sends each task to the right person inside the project of its own site.
• A developer away from the task list. The Telegram notification arrives together with the task.
• The same problem reported many times. Repeats are merged with the first message instead of starting over.
• Site and app together. Messages from the website widget and from the in-app modules arrive under one project key and go through the same chain.

Limits worth knowing

The rules of bug tracking automation have edges:

• Urgency is raised only by the narrow phrase list. A message that describes a serious failure in other words is not marked as urgent by this rule.
• Different visitors are merged only when their texts reach the match threshold. Texts below it stay separate.
• The AI description is an addition. The original message stays the source of truth.
• Receiving messages and storing them happens on the Bugfix infrastructure, in a Supabase database.

Frequently asked questions

What does bug tracking automation do with a duplicate report?

An exact repeat from another visitor is merged with the original message. The same person adding the same problem is merged by word stems, and similar texts from different visitors are merged by a match threshold. A duplicate closes together with the original.

Can a task stay without an assignee?

No. The assignee is chosen from the directory “project → owner”, so every task has one.

How does the visitor learn that the bug is fixed?

When the task is closed, the message is marked as fixed and the author sees “✅ Fixed in version N” with an explanation.

Related features

• Bug report widget
• User feedback
• In-app bug reporting