v 16.0 Third Party 84
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Project (project)
Discuss (mail)
Lines of code 515
Technical Name task_checklist
LicenseSee License tab
Websitehttps://faotools.com/apps/16.0/task-check-list-and-approval-process-16-0-task-checklist-762
Versions 18.0 17.0 10.0 8.0 15.0 11.0 14.0 16.0 9.0 13.0 12.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Project (project)
Discuss (mail)
Lines of code 515
Technical Name task_checklist
LicenseSee License tab
Websitehttps://faotools.com/apps/16.0/task-check-list-and-approval-process-16-0-task-checklist-762
Versions 18.0 17.0 10.0 8.0 15.0 11.0 14.0 16.0 9.0 13.0 12.0

When you define project stages, you consider some requirements a task should satisfy to be there and to be moved forward. Those requirements are of high importance to making projects run smoothly. Missing any step might lead to long-run troubles. To avoid those troubles use this tool. This Odoo app provides a checklist for each task stage to control requirements' fulfillment and to make sure that each action is fully approved by responsible users.

Documentation: https://faotools.com/docs/6/task-check-list-and-approval-process-37

Stage-specific project checklists

Checklists are assigned per each task stage. For instance, actions for the 'to-do' and 'in progress' stages might be different. Prepare any number of checkpoints for each project stage

Actions ensured to be done

To move a task forward through the project funnel, its checklist should be fully confirmed ('moving forward' implies any change of stage from a lesser to a bigger sequence). For certain stages - e.g. for 'Canceled' - you may want to avoid such restrictions. Then, mark this stage as 'No need for checklist'

Highlighted task progress

Fulfillment progress is shown on task kanban and form views for instant overview

Approval history for managerial control

Checklist actions are saved in history. If a task is moved back, already-done checkpoints will be recovered. Turn on the setting 'not saved' to avoid that behavior for specific approval points

Multiple task checklist roles

The app lets assign security groups for each checklist point. Then, only users from those groups will be able to confirm a related item

Prohibit stage skipping

Configure specific stages as required, so users would not be able to skip those. Then, the stages with the 'Forbid skipping this stage' option will be always visited and their checklists will be fulfilled. The setting does not influence 'No need for checklist', for example, when you cancel a task

Forbid task regression

With the tool, configure the project pipeline to disallow moving tasks back. To that goal, turn on the option 'Forbid regression to this stage' for particular states. For example, to make sure no tasks become 'Under consideration' again

Super approval admins

The special role 'Checklist Super User' allows (a) to confirm any checkpoints disregarding defined security groups and (b) to move any task further (progress) without fulfilling checklists; (c) skip any states; (d) to move any task back (regress) even a new stage does not allow that.

If set to "true", a task might be moved to this stage without fulfilling a check list. Usually used for "cancelled" stage, since cancelling doesn't need any sort of extra actions. In such a case users can move any task to "cancelled" from any stage without doing anything (e.g. new > cancelled, in progress > cancelled).

If set to "false", a checklist of a current stage is required to be entered if moved to this stage (in case it is further through the pipeline). For example, "done" state requires certain actions. If you move a task from "under approval" to "done", you should confirm check points of the "under approval" stage. "False" is the default value for "no need for checklist" field.

Anybody who has access to stage settings can modify the value of check lists.

Please, make sure, that your user hasn't "Task Checklist Super User" rights. As they allow to confirm any checkpoints disregarding chosen security groups and to move any task further without fulfilling any of them.

When making a checklist you can choose the user groups for each checklist's statement. Only these user groups will be able to mark the statement as done. If someone else tries to mark the statement done, then the system will not let them save it and the warning will appear.

According to the current Odoo Apps Store policies:

  • every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
  • starting from version 13.0, every module version should be purchased separately.
  • disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.

Take into account that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.

The easiest approach is to use the Odoo store built-in workflow:

1. Open the module's page and click the button Deploy on odoo.sh

2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project

3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.

These steps will install the app for your project production branch. If you want to deploy the apps for other branches or update the module, you should undertake the following actions:

1. Upload the source code for the app from the Odoo store

2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions

3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.

  1. Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;

  2. Re-start the Odoo server;

  3. Turn on the developer mode (technical settings);

  4. Update the apps' list (the apps' menu);

  5. Find the app and push the button 'Install';

  6. Follow the guidelines on the app's page if those exist.

Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.

A red/orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.

So, first of all, please check deployed database features. Does everything work correctly?

If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).

Regretfully, we do not have a technical possibility to provide individual prices.

No, third party apps can not be used on Odoo Online.

Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.  

The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.

Odoo demonstration databases (live previews)

For this app, we might provide a free personalized demo database.

To demand such a database, press the button "Live Preview" on the top of this page or copy the link https://faotools.com/s/ruqjif

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

By your request, we will prepare an individual live preview database, where you would be able to apply any tests and check assumptions for 14 days.

Bug reporting

In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.

To send us a bug report: press the "Website" link on the top of this page and push the button "Bug Report" (the tab Support). Alternatively, copy the link https://faotools.com/s/y6v0fu

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).

Public features requests and module ideas (free development)

We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.

Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.

To share ideas: press the "Website" link on the top of this page and push the button "Share Features Ideas" (the tab Support). Alternatively, copy the link https://faotools.com/s/4j2669

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

Questions and misc issues

Feel free to contact us with any other concerns, doubts, or questions: press the "Website" link on the top of this page and push the button "Raise Question" (the tab Support). Alternatively, copy the link https://faotools.com/s/aksicp

About the team

faOtools (faotools.com, former odootools.com) is the team of developers and business analysts to help you extend Odoo's potential. We have been communicating with end users to whom the software became the main business tool since 2012. As a result, we are proud of dozens of successful Odoo apps developed. We are open for new ideas and challenges to create the best Odoo apps for business needs all over the world.

You may like the tools

Cloud Storage Solutions

The tool to flexibly structure Odoo attachments in folders and synchronize directories with cloud clients: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, and Dropbox. DMS. File Manager. Document management system

245 220
KnowSystem: Knowledge Base System

The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.

298
OneDrive / SharePoint Odoo Integration

The tool to automatically synchronize Odoo attachments with OneDrive files in both ways

394 354
Google Drive Odoo Integration

The tool to automatically synchronize Odoo attachments with Google Drive files in both ways

394 354
Universal Appointments and Time Reservations

The tool for time-based service management from booking appointments to sales and reviews

398
Task Auto Numbering and Search

The tool to quickly access and simply reference tasks by automatic numbers. Project tasks sequence. Project task numbering

48
Custom Fields for Projects

The tool to add new fields for Odoo projects without any technical knowledge

38
Custom Fields for Tasks

The tool to add new fields for Odoo project tasks without any technical knowledge

38
Tasks Daily Reminder

The tool notifies users of assigned to them topical tasks

18
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.