NextERP Documentation
ROEN

Working with NextERP · Article 01

Project Workflow

Applies to Odoo 19 · 20

The standard process through which a development request goes from helpdesk ticket to production. It covers opening the ticket, documenting the specification in the ticket, converting it into a project task, the estimate, the approval, the development, testing on runboat and the final documentation.

🎫 Step 1 — Helpdesk ticket (Category: Development)

Every development request starts with a helpdesk ticket opened by the customer in the portal (see the "Support procedure" article). In the form, select:

  • Category = Development
  • Priority, Mediu, Version — filled in as usual
  • Subject — concise: which feature / flow change is requested
  • Description — the initial description (see the "Documenting the specification" section below)

The ticket becomes the place where the specification is documented. All clarifications, decisions and attachments stay on the ticket for audit.

📝 Step 2 — Documenting the specification in a Knowledge article

In the Helpdesk ticket description, add a link to a dedicated Knowledge article, in which the complete specification is documented. The Helpdesk ticket remains the official place of the request (audit, communication, SLA) — the Knowledge article is the working place of the specification.

  1. Creating the article — the Project Manager creates a new article in Knowledge (under a dedicated specifications workspace for the project / customer).
  2. Loading the template — the "Software Specification" template is inserted into the article (from the Insert template button of the Knowledge editor); it already comes structured with the 3 mandatory sections.
  3. Adding the link to the ticket — the link to the Knowledge article goes into the Helpdesk ticket description (or as the first message in the chatter), so that everyone involved can find it.
  4. Documenting the changes — all necessary changes are documented iteratively in the article, filling in the 3 sections:
    • Description Background — the importance within the existing flows (why it is needed, what problem it solves).
    • Functional Description — adding / changing the flow with new steps (from a business point of view).
    • Technical Specification — technical details of the code to be added / changed (models, fields, overrides, views).

Details about each section and complete examples: https://www.nexterp.ro/specification-example

👥 Who fills in what

  • Description Background + Functional Description — filled in by the Project Manager, either on the customer's side or assigned by NextERP. Discussions with the customer take place on the Helpdesk ticket; the result (the finalised text) goes into the Knowledge article.
  • Technical Specification — filled in by the assigned developer in the Knowledge article, after the first 2 sections are finalised.

As long as the Knowledge article is not complete (all 3 sections covered), the Helpdesk ticket stays in On Hold status. Once the documentation is finished, move on to Step 3.

🔄 Step 3 — Converting the ticket into a project task

Once the specification is complete (all 3 sections covered and approved by the customer), the support team converts the ticket into a task in the corresponding implementation project:

  • The new task copies the specification description from the ticket.
  • The task has a helpdesk_ticket_id field that points back to the original ticket.
  • The Helpdesk ticket goes to On Hold while development is in progress.
  • The relevant attachments are copied to the task.

The rest of the flow (estimate, approval, implementation, testing, done) takes place on the project task, NOT on the original ticket.

💰 Invoicing the specification time + technical analysis

  • If the PM is assigned by NextERP, the hours needed to take over and detail the specification (on the Helpdesk ticket) are invoiced at the rate in the contract, under the "Odoo Implementation Services" service type.
  • The time spent on technical analysis (Technical Specification, filled in by the developer on the ticket) is invoiced at the same rate.

⏱️ Implementation time estimate

After the technical specification is complete, the developer estimates the total time. The estimate includes:

  • Detailing the task
  • Technical analysis
  • The actual code development
  • Code review / testing
  • Writing the documentation

✅ Estimate approval

Once the estimate is finalised, it is sent to the customer for approval. You will receive an email notification for each ticket that needs approval. Approval is given from the customer portal, on each task separately.

Total time invoiced = the approved value. It cannot be changed later by either the Project Manager or the developer.

After approval, the task automatically goes to "in progress" status and a developer takes it over for implementation. In this phase, the developer updates the planning data and the development deadline.

🚫 Cancellation after the estimate

If, after receiving the estimate, you decide not to implement the task, you can close it directly from the portal. The time already logged for detailing and analysis is invoiced at the rate in the contract (Odoo Implementation Services).

🧪 Ticket testing approval

Once the implementation is finished, the ticket goes to "testing" status. The customer approves completion after testing in:

  • Their own test environment (if there is one), OR
  • Our test environment, runboat — see the dedicated "Runboat — the test environment" article for access, login and the actions available per instance.

For minor bugs found during testing, reassign the task to the developer for corrections.

🏁 Done → documentation → production

After you have tested and approved the task from the portal, it goes to "done" status. In this status:

  1. The functional documentation is written — text in a specific document or a video recording.
  2. After the documentation is written, the task can also be deployed to the production environment.

📞 Contact

Documentation by the NextERP team.