Support and LTS

Odoo support after go-live

Tickets, fixes, changes and updates

At a glance

  1. Tickets, bug fixes, change requests and updates.

  2. A ticket agent proposes a line-level fix plan.

  3. A person approves the plan before any code is written.

  4. Test on staging, then a pull request that a person merges.

How a fix goes livePersonTicketbug or change requestTicket agentFix planline-levelPersonApprovalbefore any codeStagingTest on stagingred before, green after the fixPersonMergepull request, then live
How a fix goes live An agent proposes, people decide: approval before the code, merge after the test.

Simplify-ERP looks after Odoo systems after go-live: tickets, bug fixes, change requests and updates. Every fix is approved as a plan first and tested on a staging system before it goes live. A ticket agent proposes the fix plan, a person approves it, and each fix arrives as a pull request that a person merges.

Details

What support covers

  • Tickets

    Reports from users are recorded and handled as tickets.

  • Bug fixes

    Reported bugs are fixed.

  • Change requests

    New requirements from day-to-day operation are implemented.

  • Updates and maintenance

    The system is kept up to date and maintained.

How a fix goes live

  • 1. Fix plan

    A ticket agent proposes a line-level fix plan; a person approves it before any code is written.

  • 2. Test on staging

    The approved change is tested causally on the customer's staging system: red before, green after the fix, red again on revert.

  • 3. Pull request

    Each fix arrives as a pull request marked tested or not tested with manual test steps; a person merges it.

  • 4. Live

    Only after approval and a test on the staging system does the fix go live.

Key facts

Scope
Tickets, bug fixes, change requests, updates
Before code is written
Fix plan approved by a person
Test
On the customer's staging system
Version upgrades
With LUDO

FAQ

Frequently asked questions

What does support after go-live cover?

Tickets, bug fixes, change requests, updates and system maintenance.

Does an AI change our system without control?

No. A ticket agent proposes a line-level fix plan, and a person approves it before any code is written. The fix arrives as a pull request marked tested or not tested with manual test steps, and a person merges it.

What does "tested causally" mean?

On the staging system the test fails before the fix, passes after it and fails again when the fix is reverted. That shows the fix, and nothing else, made the difference.

Why test on a staging system at all?

A staging system is separate from the live system, so a change can be checked there before it reaches the data your company works with every day.

Questions about your project?

Talk your starting point through with us.

Free 30 min -- no obligation