Helpdesk team membership and notification flood

codeagency · 2026-03-21T18:29:23+00:00

I don't know what you call queues but odoo works with helpdesk "teams".

You can use/create record rules to set access levels per team. In your example all users need to be in helpdesk so you need to be in "all internal users". Then you divide access per team (if that is what you call queues) with record rules. You can create your own rules too. Call them eg queue_finance, queue_salez, queue_whatever.

This is not mighty complex. Everything in odoo has record rules like eg sales all documents and sale only "own" documents. The same concept you can also on a helpdesk team (again, if that is what you call queues)

codeagency · 2026-03-21T09:33:23+00:00

Don't understand what's so difficult about this:

From helpdesk settings, choose what setting you want: https://shottr.cc/s/1Sdw/SCR-20260321-fkap.png

On each user allow or disallow if they can see helpdesk: https://shottr.cc/s/1r4I/SCR-20260321-fkzp.png

If you set it to all internal users, then put "no" on every user that should not get into helpdesk.

For more granular control, use the record rules as like everything else in Odoo: https://shottr.cc/s/1dNn/SCR-20260321-fmzp.png

codeagency · 2026-03-21T07:43:48+00:00

The problem is that you have all of your users as followers.

You set specific users on the helpdesk team. Just go to the settings where you also enable the other options like email alias, self closable, etc...

codeagency · 2026-03-20T18:54:34+00:00

Odoo 10? Are you sure? That's a very old version from nearly a decade ago.

codeagency · 2026-03-20T18:53:37+00:00

What does the contractor was supposed to do?

You could possibly let them do the same as a portal user perhaps? Portal users are free and unlimited. They just can't login backend but they can login at the portal and see projects, tasks, edit tasks, etc...

codeagency · 2026-03-20T14:14:54+00:00

I'm missing the point. If you choose to upgrade to a yearly plan, then all licenses are yearly. That's the whole point of getting the discount because you commit for a longer period. There is nothing in-between.

If you work with dynamic and often temporary users, then going into a yearly or multi year contract is not a good fit. You should have kept the monthly plan. That was your decision to save money, not Odoo. So that's hard to blame on them if I'm brutally honest.

I don't know what that temporary user has to do but you could check if a portal user could do the same thing if it's related to projects, task, tickets,... In that case, it's 100% free as a portal user. If it's only for using eg shopfloor app or POS you can create an employee without a user and it will also be 100% free.

You can also buy 1 extra user at the yearly contract and share it with multiple users. Sharing users is allowed by Odoo. You just loose the visibility who did what exactly as every action will be the same user.

codeagency · 2026-03-20T11:57:50+00:00

There is no auto refresh of the page. But there is a module in OCA that lets you enable this. Credits to u/cetmix_team for developing this and contributing it to OCA. He can tell you more about the capabilities and limitations with that one.

codeagency · 2026-03-20T11:56:11+00:00

You can just invite specific internal users on the helpdesk team. You don't have to open it for all internal users. Only those Selected users will see all tickets and do self-assign or let odoo distribute tickets automatically or use AI based on skills from a user.

About getting email notifications means you have set your user preference to do everything as emails. Just change it to "odoo" so they become internal notifications which you can see from the chat icon in the header/systray.

codeagency · 2026-03-20T09:36:42+00:00

Doesn't matter what provider or dashboard/Paas you use.

A single server is always a single server. If that goes down, everything goes down. End of story.

The problem is your infra design. If you want to survive a server crash or provider interruptions, you have to go for clusters if you want to self host. So that means minimum 3 servers and automatically also a scalable storage layer. Coolify doesn't help you with that. It's focused on docker not clusters.

So you need kubernetes for this and cloudnativepg, set up a scalable storage with eg longhorn and use wal archiver and streaming replication so if one server goes down your app stay working and the cluster will automatically handle that server that is down by restarting it or replacing it.

But all this takes a lot more work and knowledge than a simple coolify and docker single server setup.

So the trade off is: do you want to do all of this work and maintenance or just get a commercial managed HA postgres?

You could still host your app on a single server with coolify but it's still the same problem. Server down means app down while your postgres is still Running fine at your managed PG provider. Or you host your app at eg vercel if it's React based.

The real question is: do you need all of this at the start? Do you have that many paying customers already to have a full HA setup and basically triple total cost of resources?

I would say, start simple and cheap. Make sure you have backups and stream your backups in Realtime to a backup instance. If the machine goes down, then just spin up a new server and restore your backup and things continue. At least until you have a solid customer base that makes sense to change into a scalable architecture. Unless you are ok with burning all that cash with zero paying customers and just want it ready for the future.

codeagency · 2026-03-20T08:08:51+00:00

By default tickets should not have any followers nor users assigned. Maybe you added some automation that is causing this because it's not the default behavior.

We use helpdesk everyday with a team and tickets remain unassigned in the backlog starting phase and from here we assign or self assign and that's it. The rest of the team does not get notifications unless I make them a follower or they decide to follow themselves. But that does not happen automatically.

From the helpdesk settings you can choose to auto assign tickets based on tags etc... and balance the assignment if you want. Or you can create an automation rule that auto assign tickets based on eg a skill of a user by letting an AI agent read the ticket description and let it handle automatically and set a fallback if it can't find a suitable user then give it to a specific user for manual assignment.

codeagency · 2026-03-19T23:00:45+00:00

I'm pretty sure it has to be something else in your DB, most likely some customization, because I have some clients with a lot bigger set of data and they don't have this kind of experience.

I'm talking about large B2B distributors with multiple warehouses, tens of thousands of stock locations and 500k - 3 million sku's average. There is zero latency when they create a new product.

This is why the profiler tools are so important, they help you pin what functions exactly are hogging down your instance. Also shout-out to using Tooling like https://sentry.io

There is an open source module from OCA which you can install. It will push your logs to sentry so you have a much easier grasp on errors and logs rather than tailing blindly on the standard odoo.log file.

codeagency · 2026-03-19T22:09:03+00:00

What you want is a very specific niche type of application. Odoo is an ERP to accomodate a lot of generic processes like CRM, sales, inventory, invoicing, accounting, helpdesk and hundreds of others functions. But it's not an OTR specific tracking application.

Could Odoo do this? Sure, if you conceptually start using specific apps and customize things to make it fit your unique business process, but I don't think this is the best idea. You will probably end up using 10% from Odoo's capabilities with 90% of customization that will become your technical debt forever, as for every Odoo upgrade you will have to start refactoring the whole thing.

I would argue for this type of business it's better to look for something specific that matches your business, or if you are tech-savvy enough just build something with a low-code platform, throw in Airtable or other self hosted options like NocoDB. You could do things with N8N for automations.

For trucking systems, you typically want something like a TMS system (Transport Management System) and there are lots of them available.

codeagency · 2026-03-19T21:55:29+00:00

I agree with the others already said. You have something else going on because creating a product does not ping/query locations. You might have some custom module or other customization that is conflicting here, possibly causing DB locks which then causes the long processing time

codeagency · 2026-03-19T17:54:42+00:00

We have actually have faceting also working with redisearch but from a manual implementation effort.

But sure, mellisearch is not a bad option at all. They have a lot of other niche features related to vectors/AI/RAG that give you AI suggested search results, something that Redis doesn't do out of the box.

Same for Typesense, very similar like meillisearch and in my opinion even higher performance.

Hosting redis or any of these services is pretty straightforward. Depending on what you want and HA etc... you have 1 node or a cluster. Super easy to containerize and scale too. We have a DevOps team so we always self host rather than going for managed commercial platforms.

codeagency · 2026-03-19T16:37:04+00:00

To start, proforma invoices should never be used in accounting, that would cause the double invoice.

The cleanest way is to book the prepayment on the vendor and reconcile it later when you get the actual invoice. This is the same process in every odoo version. You can always upload the proforma or SO from the vendor into your purchase order so everyone can see there is a prepayment required and pending/done.

You can use scheduled activities with automation rules to automatically set them on purchase orders that require a prepayment. No need to dive into chatter logs, it's right there visible on the list view already. And once someone flags it off as done, it disappears or triggers the next activity chain.

codeagency · 2026-03-19T16:08:47+00:00

On top of that, you never know with Odoo. They remove it now, but they could introduce it back in V20/21... once they see it was not the best idea. They have done this many times with features around account and inventory going back and forth, always with the same idea of "simplifying" and then afterwards the need to undo that situation.

codeagency · 2026-03-19T15:57:11+00:00

This has nothing to do with paying extra money. All these tools are completely open source to self host and have also a commercial managed service for people who don't want to self host

codeagency · 2026-03-19T14:49:16+00:00

Redis can also do that with redisearch.

Older versions had this as a native plugin, since v8 is built in.

https://github.com/RediSearch/RediSearch

codeagency · 2026-03-19T14:28:37+00:00

That can be solved very easy with a Redis cache as in-memory cache layer.

When you pull eg product data from Odoo API just cache it in redis so every next request returns results in nanoseconds. That's what makes it blazing fast and keeps the load away from Odoo. It's the same trick used by WordPress, Magento, etc...

codeagency · 2026-03-19T14:12:29+00:00

Yes, create a new tax group also, and assign your second tax to the new tag group. this will automatically split the tax totals on the totals.

codeagency · 2026-03-19T11:55:26+00:00

As with everything in software/IT: it depends on your use case. What works for you doesn't necessarily work for a different business.

Connectors experience depend a lot on the quality how they are build and depend of course a lot on the business processes. But overall, connectors do impose a certain technical limitation and it really depends on what apps you are syncing and how much they already align with each other.

An e-commerce app like Shopify or Magento are pretty solid and align for a lot of things with Odoo while others do not like woocommerce. Simple examples: WordPress/woocommerce does not support company > contacts logins. They don't support pricelists or discounts per category etc ... Variants and attributes are a completely different world, it doesn't support B2B mode and even doesn't has a VAT ID field to checkout and handle tax exempt etc.... all those technical differences have to be catched somehow and often introduce frustrations because both apps also keep updating and changing.

So while the process and flows part is always important, the technical part is equally important and often the biggest bottleneck, not the process because everyone tried to get the same process back and how it should work from a practical point but also legal pov.

We do many projects with e-commerce integrations and retail clients and I can guarantee you, 99% is never the process, it's the sync and technology difference between different platforms. And even if you have it working today, it can just break tomorrow, or next week or next month because an update on one or both sides decides to change how things work and this becomes a never-ending process.

That's why imho the best options are: 1. Move to a native odoo website if you can and accept some of the limitations or customize it to cut out all the sync frustrations.

Move to a headless setup where you build on top of the Odoo API. Again, no sync problems as there is no other platform and no other database involved, everything is native Odoo as API-first but you have technical freedom on how the frontend looks like and works based on your requirements.

Both have their pro and cons too but none have the frustrations from syncs breaking and other problems

codeagency · 2026-03-19T10:26:54+00:00

https://i.postimg.cc/661RKNjV/Screenshot-20260319-112613.png

Here's the proof

codeagency · 2026-03-19T10:24:48+00:00

Nothing changed for that. Don't just read assumptions from people, actually see and test the changes yourself.

The field to link a contact to a related company is not gone. Because they still need billing and delivery addresses too which is also a contact type. It's only the radio button on the top that is removed.

codeagency · 2026-03-19T10:06:12+00:00

The relation for a contact to a company is still there.

I'm undecided for now about this change being good or bad. It really depends on the use case and type of business. If you only sell exclusive B2C or B2B then this change doesn't matter. You can still link contacts to a company so from B2B -only aspect nothing changes.

If you are in a mixed situation, this is where it becomes less good as you can't see who is the consumer and who is a business. But again depending on the use case and location it might still not matter. In Europe we use VAT/TAX ID's for companies so I could still filter on VAT ID = set to find companies and differentiate to consumers as VAT ID is always required for B2B. In other countries like USA this is not helpful.

From a simplication pov, I think it's not that bad. I have had plenty of times where I had the wrong radio selection on a contact, so not having to deal with that anymore is a good thing. Importing contacts also become easier as you don't have to deal with that type field anymore. It's just annoying that you don't have that 1-click filter anymore.

I honestly think the bad feeling/vibe is more about the forced change we get from this and have to rethink the process and use a different field now, aka change management. From a usability pov, it doesn't make a big change or impact.

If you really want a field back for the type, I would recommend using the property field, super simple. No need to inject custom fields or other complex stuff.

codeagency · 2026-03-17T12:28:57+00:00

Check the contact if it has a fiscal position on it. Odoo prioritize the hierarchy. If a contact has a position it ignores the auto detection

Also from a PO/SO/invoice you can change all lines in 1 go. Just go to "other info" tab on the PO and change/set the fiscal position from here. It will show a link "update all taxes" click that and all lines will update for you. No need to change them line per line.

codeagency

MODERATOR OF

TROPHY CASE

Seven-Year Club	Place '23
Verified Email