Odoo is well established company. I can't create something that big and professional alone. I can only build a very small project with some basic features.Thank you for taking my wish into consideration.
very similar to blog dashboard management,
User Management,
customer list,
shop list, tool list,
ticket management
chatt (blog type) on the ticket,
tickets open, closed, in progress
customer / ticket reports
here is an example
Odoo Helpdesk
Gestisci il tuo servizio clienti con Odoo Helpdesk, che è ottimizzato per la produttività del tuo teamwww.odoo.com
main functions would be fine tooOdoo is well established company. I can't create something that big and professional alone. I can only build a very small project with some basic features.
AdminLTE3 has only the design as placeholder. The functions are added or customized based on users requirements.your dashboard is very close to what I need, if it already works and they are not just screen shots
[Project Template] [Web] API Server 2
Version: 2.07 Description: Create Web API Server using B4X project template Sample project: Support Ticketing System If you don't want to connect to any SQL database, see MinimaList API Server For older version, see Web API Server (v1.16) Template: Web API Server (2.07).b4xtemplate...www.b4x.com
chatt?chatt (blog type) on the ticket
unfortunately on the web I'm completely fasting I couldn't give you any indicationsAnd how about the technical specification?
What kind of database you want it to use? SQLite, MySQL or others?
What front-ends? Using popular framework like Vue or React, just any JavaScript or jQuery will do? HTMX? Bootstrap? don't care?
as far as the tables are concerned, they should be more or less organized like this:I want to know what are the common features people are looking for. With the price to justify the scope.
My thoughts may be very different from others.
Customer management - a CRM system? or just a simple table just to keep some fields like email and contact?
Shop - just for a drop down list with id and name?
Equipment management - also another table? What are the fields? Some simple fields, you would add more fields your own?
Are there categories for the above? For example, you have different type of customers, Shop by State, City or Region and Equipment is categorized by Department or types?
Ticket Management - Customer can create own ticket or only created by a support officer? Allow upload of images? Keep track of SLA? Email? Live chat? Export or print?
Assistance management for Equipment meaning? is it like warranty or contract agreement?
Every ticket is chargeable? Cost Centre?
Reporting and Dashboard? What reports are required? What summary you want to see in Dashboard?
User Access Permission and Roles?
If the poll closed and less than 10 people are interested then I am not going to build one. I don't want to create something that low in quality or useless and sell like $5 for 2 people, or I have spent like 3 months and more to build with high quality features and then also sell very bad.
clearly if you have to do it just for me, the price would be very high, if you do it for the community, the price could be low, since you would sell many copies as many here do.
And how about the technical specification?
What kind of database you want it to use? SQLite, MySQL or others?
What front-ends? Using popular framework like Vue or React, just any JavaScript or jQuery will do? HTMX? Bootstrap? don't care?
in fact, I'm better off with mysql, or mssqlI believe the possibility of dragging and dropping files is very useful
And therefore I would choose a framework that allows this function (if it exists)
As for the database to use, I believe that now one equals the other
Personally I would use Firebird, it's free, powerful, usable also in production, but I wouldn't consider the choice of the db as an essential feature
Everyone will put the one with which he is more comfortable
in fact, I'm better off with mysql, or mssql
as well as sqlite