Odoo Help


v7 - How to "query-insert" a stage change in a task journal ?

François Dubois
on 11/8/16, 7:34 AM 605 views

Hello all,

When I am in a task, if I change the stage of this task, a log is generated in the journal at the bottom on the task page like this :


Now, I would like to do the same thing using postgreSQL query :

I succeed to update the current stage of the task (in table project_task, then I insert a line in the table project_task_history to save the action of "stage changed", but when I refresh the page, the stage change is not saved in the journal ar the bottom of the task page ...

Do I miss something so that the task change is inserted in this journal ?

Can someone help me please ?

Thanks a lot in advance.

why do you want to do it in sql ? At first view, It's seems a bad idea !

Jérémy Kersten (jke)
on 11/8/16, 8:55 AM

Thanks Jérémy Kersten for helping me.

I would like to do this, so that I can generate a report based on the database later. I will need to calculate duration between two stages, so I need to log these stage-changes. Of course I can let the users of the project do it themselves with their mouse/keyboard using the UI, but it'll be better for me to automatically change stage of tasks once their deadline_date is over.

Also, sometimes we will have a lot of tasks to stage-change, so it would be great if I can do it automatically. Actually I can do it, but my problem is that no log is generated to say "previous stage => next stage", and I need a date to create a report in the future.

Thanks a lot.

François Dubois
on 11/8/16, 9:14 AM
François Dubois
On 11/8/16, 9:02 AM

Thanks Jeremy. 

You mean create a scheduled action via odoo ? 

Because I already do it using postgreSQL queries, it's working but like I said, the link "previous stage > new stage" is not done ... 

when you do it in sql, you bybass the write function of odoo which do the job...

You can do it in sql, with a message post, and reimplementing the logic of tracked field, but it is a really bad idea according to me...

One scheduled action that check a domain and change the stage is probably 3 lines of code... And workflow will be always ok... And you keep the logic in Odoo, you let Odoo do HIS job and you don't need to maintains 2 logics

Jérémy Kersten (jke)
on 11/8/16, 9:43 AM

Jérémy Kersten (jke)

--Jérémy Kersten (jke)--

| 3 3 5
Jodoigne, Belgium
--Jérémy Kersten (jke)--

Jérémy is a member of the core R&D team since september 2013. He developed several projects for OpenERP version 8 including the eCommerce, the Google Calendar synchronization and the new product variants/configurator. Now, he manages Odoo website and themes for saas.

Jérémy Kersten (jke)
On 11/8/16, 9:16 AM

Ok... so

Why not add a scheduled action that will check all deadline_date > now and stage != your_new_stage, and if needed change the stage...

Like that, you let Odoo make the job with all the workflow, and tracked fields will be correctly set...

Seems  the right way...

About This Community

This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.


Odoo Training Center

Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.

Test it now

Question tools

2 follower(s)


Asked: 11/8/16, 7:34 AM
Seen: 605 times
Last updated: 11/8/16, 9:18 AM