| Server IP : 127.0.0.2 / Your IP : 3.145.216.39 Web Server : Apache/2.4.18 (Ubuntu) System : User : www-data ( ) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : disk_free_space,disk_total_space,diskfreespace,dl,exec,fpaththru,getmyuid,getmypid,highlight_file,ignore_user_abord,leak,listen,link,opcache_get_configuration,opcache_get_status,passthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,php_uname,phpinfo,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwnam,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,pclose,popen,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,shell_exec,source,show_source,system,virtual MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /opt/odoo/addons/project/doc/ |
Upload File : |
.. _stage_status: Stage and Status ================ .. versionchanged:: 8.0 saas-2 state/stage cleaning Stage +++++ This revision removed the concept of state on project.task objects. The ``state`` field has been totally removed and replaced by stages, using ``stage_id``. The following models are impacted: - ``project.task`` now use only stages. However a convention still exists about 'New' stage. A task is consdered as ``new`` when it has the following properties: - ``stage_id and stage_id.sequence = 1`` - ``project.task.type`` do not have any ``state`` field anymore. - ``project.task.report`` do not have any ``state`` field anymore. By default a newly created task is in a new stage. It means that it will fetch the stage having ``sequence = 1``. Stage mangement is done using the kanban view or the clikable statusbar. It is not done using buttons anymore. Stage analysis ++++++++++++++ Stage analysis can be performed using the newly introduced ``date_last_stage_update`` datetime field. This field is updated everytime ``stage_id`` is updated. ``project.task.report`` model also uses the ``date_last_stage_update`` field. This allows to group and analyse the time spend in the various stages. Open / Assignation date +++++++++++++++++++++++ The ``date_open`` field meaning has been updated. It is now set when the ``user_id`` (responsible) is set. It is therefore the assignation date. Subtypes ++++++++ The following subtypes are triggered on ``project.task``: - ``mt_task_new``: new tasks. Condition: ``obj.stage_id and obj.stage_id.sequence == 1`` - ``mt_task_stage``: stage changed. Condition: ``obj.stage_id and obj.stage_id.sequence != 1`` - ``mt_task_assigned``: user assigned. condition: ``obj.user_id and obj.user_id.id`` - ``mt_task_blocked``: kanban state blocked. Condition: ``obj.kanban_state == 'blocked'`` Those subtypes are also available on the ``project.project`` model and are used for the auto subscription.