We’re celebrating 10 years!


GitAdvising celebrates a decade of effort, dedication, and incredible achievements along this journey.
Thank you for joining us in this story and for being part of it.
¡Happy 10th anniversary!


Support and Requirements Management

Will be considered as Odoo Support:


Our functional support service for Odoo includes the resolution of basic technical issues within the system, as well as the handling of errors that may interrupt daily operations.

We also provide support for incidents related to access and permissions, as well as guidance to resolve questions about processes previously reviewed during training.

The service includes the detection and correction of operational errors made by users, as well as the necessary guidance to ensure the proper use of the platform and prevent future incidents.

  • Support assistance is provided exclusively through the creation of tickets through our portal soporte.gitadvising.com, with the purpose of ensuring proper follow-up, maintaining incident control, and guaranteeing organized response times.

Will be considered as a New Requirement:

A new requirement is considered to be any request for development, improvement, or modification of the system made by the user with the objective of covering an operational need or improving an existing functionality.

All requirements must be registered and managed through the ticket portal soporte.gitadvising.com, where a tracking number will be assigned for control and follow-up.

Depending on its complexity and impact on the operation process, the requirement may:

  • Require the preparation of a Functional Specification (FS) when the change involves modifications to the operation process or requires structured development.
  • Be managed directly through a ticket when it consists of minor adjustments that do not alter the workflow and do not require detailed documentation.


Ticket Process

Important:

The user can check the status of their ticket at any time through the support portal using their tracking number.

1. USUARIO LEVANTA TICKET

Todos los tickets se gestionan a través del portal de soporte, donde se asigna un número de seguimiento para su control y atención.

2. CONSULTOR ATIENDE TICKET

(Solicitar información extra)
El consultor analiza el ticket y, si es necesario, solicita información adicional al usuario para comprender y atender la solicitud.

3. CLIENTE REVISA TICKET

(Dar retroalimentación)
El cliente revisa la información solicitada o las actualizaciones realizadas por el consultor y proporciona la retroalimentación necesaria.

4. SOLUCIÓN DE TICKET

El consultor realiza las acciones necesarias para dar solución al ticket de acuerdo con la información proporcionada.

5. REVISIÓN DE SOLUCIÓN

El cliente revisa la solución propuesta por el consultor para validar que su solicitud fue atendida correctamente.

6. CIERRE DE TICKET

Una vez validada la solución por el cliente, se procede al cierre del ticket en el portal.

Proceso de Nuevos Requerimientos

1. Análisis de requerimiento

2. Elaborar Especificación Funcional (EF)

3. Entrega de EF
a cliente para aprobación

4. Aprobación
de cliente

5. Inicio de
desarrollo de EF

6. Pruebas equipo desarrollo

7. Entrega de desarrollo a Consultor solicitante

8. Pruebas unitarias

9. Manuales de uso (Video)

10. Entrega a cliente (Instancia de pruebas)

11. Aprobación de cliente

12. Autorización de pase a productivo

Términos y condiciones