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 project technician proposes a line-level fix plan.

  3. The customer approves the plan before any code is written.

  4. Test on staging, then a pull request that is merged after review.

How a fix goes liveCustomerTicketbug or change requestProject technicianFix planline-levelCustomerApprovalbefore any codeStagingTest on stagingred before, green after the fixProject technicianMergepull request, after reviewProduction systemLiveafter approval and test
How a fix goes live The customer reports a ticket and approves the project technician's fix plan before any code is written; after the test on staging the fix is merged and goes live on the production system.

Diagram as text

Lanes: Customer, Project technician, Staging, Production system

  1. Customer: Ticket (bug or change request)
  2. Project technician: Fix plan (line-level)
  3. Customer: Approval (before any code)
  4. Staging: Test on staging (red before, green after the fix)
  5. Project technician: Merge (pull request, after review)
  6. Production system: Live (after approval and test)

Simplify-ERP looks after Odoo systems after go-live: tickets, bug fixes, change requests and updates. The customer approves every fix as a plan first, and it is tested on a staging system before it goes live. A project technician proposes the fix plan, the customer approves it, and each fix arrives as a pull request that is merged after review.

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 project technician proposes a line-level fix plan; the customer 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, and is merged after review.

  • 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 the customer
Test
On the customer's staging system
Version upgrades
Odoo version upgrades, incl. custom modules

FAQ

Frequently asked questions

What does support after go-live cover?

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

Is our system changed without control?

No. A project technician proposes a line-level fix plan, and the customer approves it before any code is written. The fix arrives as a pull request marked tested or not tested with manual test steps, and is merged after review.

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