NutsNBolts · Bista's delivery platform

Your Odoo project, in the same workspace our team runs it on.

NutsNBolts is the platform Bista uses to develop, deploy and manage every client project. When you work with us, your team gets access too. You can follow each ticket, test work on your own Odoo instance, approve releases and see real project status, all backed by what Bista has learned across hundreds of Odoo projects.

1 workspace instead of 4–5 tools 13-stage ticket workflow on every project AI at every stage, reviewed by people
At a glance

What is NutsNBolts?

Definition
Bista Solutions' in-house platform for developing, deploying and managing Odoo projects. Ticketing, source code, AI assistance, test environments, releases and reporting sit in one web workspace.
Who uses it
Bista project managers, developers and QA on every active project, and customer teams who get access to collaborate on their own project.
What customers do in it
Follow and comment on tickets, attach files, test work on dedicated Odoo test instances, review releases and release notes, and receive status updates and KPIs.
Built on
Two-way sync with Redmine (tickets) and GitHub (code), with AI helpers for estimation, Odoo module generation, UAT scripts, release notes and status summaries.
Process
Every ticket on every project follows the same 13-stage lifecycle, from New to Closed, and the same release process.
Availability
Included with Bista Odoo projects. It's built and maintained by Bista's own engineering team and isn't sold as separate software.

Provided by Bista Solutions, an Odoo Gold Partner and 8-time Odoo Best Partner for North America.

For customers

No more "what's the status?" emails

Most ERP projects run on email threads, spreadsheets and screenshots. On a Bista project, your team works in the same system as ours, so everyone sees the same tickets, environments and releases.

See the real status of every ticket

A live board shows where each requirement, bug and change request is, who owns it and what's overdue.

Kanban · list · filters

Collaborate on the ticket itself

Comment, @mention the team and attach files directly on the ticket, not in side-channel chats. The full history stays with the work.

activity · files · @mentions

Test on your own Odoo instance

Open a dedicated Epic test instance built for a ticket or release, and run UAT with generated test scripts.

Epic · UAT · Open URL

Know what's shipping and when

Releases bundle the tickets that ship together, with a date and status, plus a release note you can share with your stakeholders.

Draft → Scheduled → Deployed

Get stakeholder-ready updates

Weekly status updates with ticket statistics, priorities and a written summary are drafted by AI and reviewed by your Bista PM before they reach you.

status update · email

Measure delivery, not just activity

KPIs show open and closed work, cycle time, throughput over 12 weeks, workload and the oldest open tickets.

KPI dashboard
Bista's knowledge, applied to your project

Your project starts with everything we've already built

NutsNBolts isn't just a project tracker. It's where Bista's Odoo experience is stored and reused: modules, conventions, process and project history. Your project draws on all of it from day one.

APPS

A catalog of proven Odoo modules

Bista's Odoo module catalog sits inside the platform, so developers start from tested building blocks instead of writing everything from scratch.

AI DEVELOPER

AI that reads your code

The AI Developer works inside your project's repository. It follows your existing modules and conventions and targets your exact Odoo version, and a developer reviews every result.

ESTIMATION

Estimates informed by past projects

Effort suggestions draw on the ticket description and the team's historical patterns. Your PM reviews and adjusts them before they're shared.

PROCESS

One delivery process, refined on every project

The same 13-stage workflow and release process run on every Bista project, so what we learn on one engagement improves the next.

AI CONTEXT

Project context that stays

Business rules, decisions and requirements are captured as project context. AI helpers and new team members build on them instead of starting over.

CONTINUITY

Nothing leaves when people change

Tickets, code, discussion, test history and releases live in one place, so onboarding a new developer or PM is fast and your project history stays intact.

You don't just hire a team. You get Bista's delivery system, with everything it has learned.

Ticket lifecycle

13 stages, from request to production

Every ticket on every Bista project moves through the same stages, so you always know exactly what "in progress" means and where you're needed.

  1. ANewRequest logged
  2. BNeed DetailsYour input needed
  3. CAssignedOwner set
  4. DIn ProgressBeing built
  5. EDev CompleteCode done
  6. FUAT (Dev)You test
  7. GQA PassedBista QA signs off
  8. HReady for StagingQueued
  9. IDeployed on StagingPre-production
  10. JAcceptedYou approve
  11. KIn ProductionLive
  12. LQA FailedSent back for rework
  13. MClosedDone
Stages where your team takes part Exception path
Inside the platform

One workspace, five areas

01

Dashboard

A personal overview of assigned work, notifications and what's due.

02

Projects

Browse and switch between projects. The selected project sets the context for every page.

03

Apps

Bista's catalog of Odoo modules, ready to reuse.

04

AI Developer

Odoo module generation for a specific ticket, aware of your repository and Odoo version.

05

Epic

On-demand Odoo test instances for each ticket or release.

AI across the workflow

AI built in, not bolted on

AI assistance sits next to the ticket it relates to, at four stages of delivery. Nobody has to copy project context into a separate chat tool.

ESTIMATION

Effort sizing

Suggests effort from the ticket description and the team's historical patterns. Project managers review and adjust.

DEVELOPMENT

Odoo module generation

Generates module code for the ticket, matching your repository's conventions and Odoo version, and commits it to a branch named after the ticket.

QA

UAT scripts

Turns the ticket into step-by-step acceptance test cases, ready to run on the Epic test instance.

REPORTING

Release notes & status

Writes release notes from the actual ticket changes and drafts the weekly status update.

People stay in the loop. AI output is a draft, not a commit. A Bista developer, QA engineer or PM reviews it at every stage.
Epic test environments

Test the real thing before it goes live

Epic creates a fresh Odoo instance for a ticket or release, so you can validate work in progress on real Odoo instead of screenshots or a shared test database.

  • On demand, per ticket or releaseChoose the Odoo version and edition (Enterprise or Community).
  • A direct link for your teamOpen the instance straight from the ticket and run UAT with the generated test scripts.
  • Monitored while it runsCPU, memory, disk and uptime are visible for each instance, and it's stopped when no longer needed.
Epic · test instancesSAMPLE
#2625 Sub serial numbersOdoo 18.0 · Enterprise
running
Release 2026.09-R3Odoo 18.0 · Enterprise · 7 tickets
running
#2598 Landed cost allocationOdoo 18.0 · Enterprise
stopped
CPU 22%
Memory 41%
Disk 18%
Illustrative panel. Each instance shows version, edition, status and resource use.
Deployment & releases

Controlled, traceable releases

Every change can be traced from ticket to code to environment. Deployments follow a guided flow with checks and permissions, not ad-hoc server access.

  • 1Draft
  • 2Pending Approval
  • 3Scheduled
  • 4Deployed
  • Branch per ticketEach ticket records its Git branch, last commit, author and time.
  • Merge status by environmentIndicators show whether the change is merged into Dev, Staging and Production.
  • Validate before deployPre-flight checks run before a deployment starts, so problems surface early.
  • Guided deploymentDeploy to Dev, Staging or an Epic instance from the ticket. Production releases merge and ship as a batch.
  • Automatic follow-throughWhen a release succeeds, its tickets move to In Production and a release note is generated, with a read-only link to share.
Reporting & visibility

Project health you can see

KPI DASHBOARD

Team health per project

  • Open, closed and overdue counts
  • Average cycle time and time in each stage
  • Throughput trend over the last 12 weeks
  • Workload by assignee and an aging report
STATUS UPDATES

AI-drafted, PM-reviewed

  • Header stats and priority breakdown
  • Team workload
  • An editable written summary
  • Sent to your project's notification list
NOTIFICATIONS

Nothing slips through

  • Assignments and status changes
  • @mentions and comments
  • Release status changes and overdue alerts
  • One click to the ticket or release
The difference

A typical ERP project vs. a Bista project on NutsNBolts

Typical ERP projectBista project on NutsNBolts
Project statusWeekly email or spreadsheet, out of date by the time it arrivesLive board and KPIs, plus PM-reviewed status updates
Requirements discussionScattered across email, chat and callsOn the ticket, with full history and attachments
User acceptance testingScreenshots or a shared test databaseA dedicated Epic Odoo instance per ticket or release, with generated UAT scripts
ReleasesUnclear what shipped and whenScheduled releases, deploy checks and automatic release notes
TraceabilityHard to connect a change to its codeTicket → branch → commit → environment
ReuseEach project starts from zeroBista's module catalog, repository-aware AI and a standard process
Team changesKnowledge leaves with the peopleContext, history and decisions stay in the platform
Access & control

Role-based access for your team and ours

Everyone sees what they need. Deployment rights are granted separately for each environment.

MemberWork on tickets, comment, attach files and update status.
Project AdminManage project settings, stages, sprints and members.
Deploy accessGranted per environment: Dev, Staging and Production.
Super AdminGlobal settings, users and AI provider configuration (Bista only).
FAQ

NutsNBolts questions

What is NutsNBolts?

NutsNBolts is Bista Solutions' in-house platform for developing, deploying and managing Odoo projects. It brings ticketing (synced with Redmine), source code (synced with GitHub), AI assistance, on-demand Odoo test environments, releases and reporting into one web workspace used by Bista's project managers, developers and QA, and by customer teams collaborating on their projects.

Do customers get access to NutsNBolts?

Yes. Customer teams get role-based access to their own project. They can follow and comment on tickets, attach files, test work on Epic instances, review releases and release notes, and receive status updates.

How does NutsNBolts bring Bista's knowledge into my project?

The platform includes Bista's Odoo module catalog, an AI Developer that works inside your repository and follows its conventions, effort estimates informed by past projects, and a 13-stage delivery process used on every project. Project context and history stay in the platform, so they're never lost when team members change.

Is NutsNBolts a product I can buy?

No. NutsNBolts is built and maintained by Bista's own engineering team and is included with Bista projects. It isn't sold as standalone software.

What is an Epic test instance?

An Epic is an on-demand Odoo instance created for a ticket or release, with the Odoo version and edition (Enterprise or Community) of your choice. Your team opens it from a direct link to run user acceptance testing on work in progress before it goes to staging or production.

How is AI used, and who reviews it?

AI suggests effort estimates, generates Odoo module code for a ticket, writes UAT test scripts, and drafts release notes and status summaries. Every output is a draft that a Bista developer, QA engineer or project manager reviews before it's used.

What are the 13 ticket stages?

New, Need Details, Assigned, In Progress, Dev Complete, UAT (Dev), QA Passed, Ready for Staging, Deployed on Staging, Accepted, In Production, QA Failed and Closed.

How are deployments controlled?

Each ticket is linked to a Git branch, with merge status shown for Dev, Staging and Production. Deployments run through a guided flow with pre-flight validation, and deploy rights are granted separately for each environment. Production releases move from Draft to Pending Approval, Scheduled and Deployed.

Does NutsNBolts replace Redmine or GitHub?

No. It connects them. Status changes in NutsNBolts sync back to Redmine, code and branches live in GitHub, and a sync action refreshes both so boards and dashboards reflect the latest state.

See it for yourself

Start your Odoo project with the whole Bista team behind it.

We'll walk you through NutsNBolts on a real project: the board, an Epic test instance, a release and the KPI dashboard.

sales@bistasolutions.com · +1 (858) 401-2332 1255 W 15th St, Suite 810, Plano, TX 75075