FixControl
Engineering

From bug report to a tested change proposal

FixControl links a bug to the right project, investigates the relevant repository and documentation, and has specialized AI agents prepare a possible change.

Book a technical demoWatch the video
Changes are tested before anyone reviews themAn engineer decides what moves forwardDelivered as a pull request — never straight to the main branch
The demo

Watch the engineering flow

From a bug report to a tested change and a prepared pull request.

This video is spoken in Dutch, with Dutch captions.Dutch captions available — turn them on in the player if you want them.
Read the video transcript (in Dutch)

Een bug wordt gemeld

Een klant meldt dat de factuurexport vastloopt bij grote bestanden.

Project en repository

FixControl koppelt het ticket aan het project Facturatie en gebruikt de bijbehorende repository, documentatie en eerdere meldingen.

Agents onderzoeken de oorzaak

Gespecialiseerde agents onderzoeken het probleem en analyseren de relevante code.

Wijziging voorbereid en getest

Daarna bereidt FixControl een mogelijke wijziging voor. Die wordt getest in een afgeschermde omgeving.

Testresultaten, risico en goedkeuring

FixControl controleert de testresultaten, het risico en wie toestemming moet geven.

Een engineer beslist

Een engineer kan het voorstel goedkeuren, afwijzen of om een aanpassing vragen.

Pull request na goedkeuring

Pas na de vereiste goedkeuring wordt de wijziging als pull request voorbereid. Niet rechtstreeks op de hoofdbranch.

Step by step

What happens with a bug report

The same flow as in the video, step by step and in plain language.

  1. 01Report
    A bug is reported

    Through support, chat or your issue tracker — the report stays in the system it came from.

  2. 02Project
    FixControl finds the project and the repository

    The report is linked to the project that holds the right code and documentation.

  3. 03Research
    Agents investigate the problem

    They read the code involved, earlier reports and recent changes to find a likely cause.

  4. 04Change
    A change is prepared

    A concrete code change that addresses the cause. Nothing has been committed anywhere yet.

  5. 05Tests
    Tests are run

    The change runs in an isolated test environment; the test results are recorded with the proposal.

  6. 06Risk
    Risk and approval are determined

    FixControl determines the risk of the change and which approval your rules require.

  7. 07Decision
    An engineer decides

    The engineer sees the change, the test results and the risk — and approves, rejects or asks for adjustments.

  8. 08Pull request
    A pull request is prepared

    After the required approval the change is delivered as a pull request for normal code review. Never straight to the main branch.

Reviewable work

From analysis to reviewable work

From analysis to reviewable work
FixControl prepares the change and makes the checks that ran visible. An engineer keeps the decision about what moves forward.
Questions

Frequently asked about code automation

Does FixControl change code directly?+
No. FixControl prepares a change, tests it in an isolated environment and delivers it as a pull request after the required approval. Never straight to the main branch.
How do we know a change is safe?+
The proposal carries the tests that ran and the risk that was determined. An engineer sees those checks and decides what moves forward.
Which code does FixControl use?+
Only the repositories you link to the project. Investigation happens with read access; changes go through a pull request after approval.
Which systems does this work with?+
GitHub and GitLab for code; reports can come in through support, Slack, Teams or your issue tracker.
Keep exploring
Also see support and email automation

From customer question to a checked reply, with the right tickets, conversations and documentation.

Support-to-engineering remediation

The full path from a support ticket to a governed code fix.

GitHub integration

How prepared changes arrive as pull requests in your repositories.

See the engineering flow on a real bug

In one technical demo we walk from bug report to a tested change proposal and pull request.

Book a technical demoContact us