diff --git a/addons/project/data/web_planner_data.xml b/addons/project/data/web_planner_data.xml index 9e3f0d63056..0b2aae71788 100644 --- a/addons/project/data/web_planner_data.xml +++ b/addons/project/data/web_planner_data.xml @@ -117,10 +117,10 @@ Your Projects -

Depending on what you need and how you want to operate, there are several ways to work with Odoo. First, decide if you want to think in terms of tasks or issues. Then, activate the Timesheets app if you need it.

-

1. Learn about Tasks, Issues and Timesheets.

+

Depending on what you need and how you want to operate, there are several ways to work with Odoo. First, decide if you want to think in terms of tasks. Then, activate the Timesheets app if you need it.

+

1. Learn about Tasks and Timesheets.

-
+
@@ -138,24 +138,7 @@

Tasks are the main mechanism in Odoo and are activated by default.

-
-
-
- - - Issues - -
-
-

- A problem or request from a customer that needs to be identified, solved and followed up asap.

-

Example:

-

A customer sends a complaint to support@yourcompany.com: an Issue is automatically created into a 'Support level 1' project based on the original email from the customer.


-

To use Issues, install the Issue Tracking app. -

-
-
-
+
@@ -171,9 +154,7 @@
  • Getting statistics on how much time a task takes to be completed
  • Invoicing your customers on Time & Material projects

    • To use Timesheets, go to your Project Settings and activate:

    -

  • for Tasks: 'Log work activities on tasks'
    • -
  • for Issues: 'Activate timesheets on issues'

    • + 'project.action_config_settings')">Project Settings and activate 'Log work activities on tasks'

    You can learn more about Timesheets in the 'Use Timesheets' section of this planner.

    @@ -189,36 +170,26 @@
  • #1
    - Tasks - Issues with Timesheet
  • #2
    - Tasks - Issues with Timesheet
  • #3
    - Tasks - Issues with Timesheet
  • #4
    - Tasks - Issues with Timesheet
  • #5
    - Tasks - Issues with Timesheet
    • @@ -255,7 +226,7 @@ Kanban Stages

    It is time to think about how you will transform your activities into real projects in Odoo.
    - For that, the most important part is defining the stages of your projects. Stages are the different steps a task or an issue can go through, from its creation to its ending. They will appear in what we call the 'Kanban' view of your projects. + For that, the most important part is defining the stages of your projects. Stages are the different steps a task can go through, from its creation to its ending. They will appear in what we call the 'Kanban' view of your projects.

    @@ -371,9 +342,9 @@ Implement - Tasks & Issues + Tasks

    - Creating Tasks and/or Issues is the next step in managing your Projects.
    + Creating Tasks is the next step in managing your Projects.
    In Odoo, it is pretty straightforward, but here are some explanations you may find useful.

    @@ -390,7 +361,7 @@

    Add a Deadline
    - The deadline will help you determine if a task or issue is progressing as expected and to anticipate its next update. + The deadline will help you determine if a task is progressing as expected and to anticipate its next update.

    @@ -398,7 +369,7 @@

    Use Tags
    - Tags are complementary to your project stages: they can work as a second level categorization which is very useful if you have a lot of Tasks or Issues to manage. Also, it becomes very easy to find Tasks or Issues by typing the Tag into the main Search bar. + Tags are complementary to your project stages: they can work as a second level categorization which is very useful if you have a lot of Tasks to manage. Also, it becomes very easy to find Tasks by typing the Tag into the main Search bar.

    @@ -406,7 +377,7 @@

    Use Status Indicator
    - The Status indicator helps you manage Tasks and Issues by giving them one of 3 different colour: Grey, Green or Red. The meaning of these Statuses can be freely configured, for example: + The Status indicator helps you manage Tasks by giving them one of 3 different colour: Grey, Green or Red. The meaning of these Statuses can be freely configured, for example:

  • Grey: the Task is in progress (someone is working on it)
  • Green: the Task is ready for next stage (the job for this stage is complete)
  • Red: the Task is blocked (there's a problem)

    • @@ -417,7 +388,7 @@

    Set Priorities
    - The is used to indicate priority: in Kanban views, high priority Tasks or Issues will be displayed on top. This is particulary useful if you use a Scrum methodology to indicate the tasks for the week. Similarly to Status, you can change the meaning of the Star indicator from the Project Stages tab. + The is used to indicate priority: in Kanban views, high priority Tasks will be displayed on top. This is particulary useful if you use a Scrum methodology to indicate the tasks for the week. Similarly to Status, you can change the meaning of the Star indicator from the Project Stages tab.

    @@ -434,7 +405,7 @@
    @@ -528,7 +498,7 @@

    Invoice your customers (every month)

    - If you work on a Time & Material project, you'll probably want to extract a Timesheet of the tasks and issues to invoice directly to the customer. To do that: + If you work on a Time & Material project, you'll probably want to extract a Timesheet of the tasks to invoice directly to the customer. To do that:

    • Activate 'Allow invoicing based on timesheets' from the Human Resources Settings. @@ -536,21 +506,18 @@
    • This will add an Invoice Tasks menu in the Project module, that can be used to select the Timesheet to invoice.

    Analyze reports (every a year)

    -

    It's usually a good idea to take time to analyze your tasks and issues once a year. Here are some KPIs you should take a look at. Ask yourself 'How can they be improved?'

    +

    It's usually a good idea to take time to analyze your tasks once a year. Here are some KPIs you should take a look at. Ask yourself 'How can they be improved?'

    For tasks:

    • What is the number of missed deadlines?
    • What is the difference between initial time estimation and final time spent?
      • -
    -

    For issues:

    -
      -
    • What is the average time before an issue is assigned / closed?
      • -
    • What is the average number of working hours necessary to close an issue?
      • +
    • What is the average time before a task is assigned / closed?
      • +
    • What is the average number of working hours necessary to close a task?

    About Employees:

    • What is their average number of working hours over the year?
      • -
    • What is their average number of tasks or issues worked on / closed?
      • +
    • What is their average number of tasks worked on / closed?
    Need help with Timesheets management? Contact us now:
    @@ -601,7 +568,7 @@ We can automate steps in your workflow, for example:

  • Send an alert when a task is stuck in red for more than a few days
    • -
  • Send an automatic confirmation to all issue emails sent to your customer support
    • +
  • Send an automatic confirmation to all emails sent to your customer support
    • @@ -823,12 +790,12 @@

    Follow only what you need
    - The simplest way to use notifications is to follow a whole project: you will receive notifications for all the new and existing tasks or issues of a project. + The simplest way to use notifications is to follow a whole project: you will receive notifications for all the new and existing tasks of a project.

    Don't hesitate to select only the events you are interested in!

    -

    Another good way to limit the number of notifications you receive is to only follow your Project's 'Task Assigned' events. Then you'll be notified when a Task or Issue is created, and can manually decide if you want to be notified for its other events too.

    +

    Another good way to limit the number of notifications you receive is to only follow your Project's 'Task Assigned' events. Then you'll be notified when a Task is created, and can manually decide if you want to be notified for its other events too.

    @@ -839,10 +806,10 @@

    Rely on the chatter
    - Below every Task and Issue (or more generally, below every Document in Odoo) is an area called Chatter. + Below every Task (or more generally, below every Document in Odoo) is an area called Chatter.

    It's for logging every change, event or message related to the Document.

    -

    So if you're looking for the history of a Task, or the latest message on an Issue, simply go to the corresponding Document and you'll find it!

    +

    So if you're looking for the history of a Task, or the latest message on a Task, simply go to the corresponding Document and you'll find it!

    @@ -864,10 +831,10 @@

    - Create tasks and issues by email
    - In Odoo, every project has an email alias. If you send an email to this alias, it will automatically create a task or issue in the first stage of the project, with all the email recipients as its default followers.

    + Create tasks by email
    + In Odoo, every project has an email alias. If you send an email to this alias, it will automatically create a task in the first stage of the project, with all the email recipients as its default followers.

    - This is particularly useful to manage help and support: all incoming email from customers will be transformed into an issue that you'll be able to track easily! + This is particularly useful to manage help and support: all incoming email from customers will be transformed into a task that you'll be able to track easily!

    @@ -902,7 +869,7 @@ Ask participants to prepare
    To run an effective meeting, prepare participants beforehand. Inform them of how they are expected to contribute.

    - For example, risk and issue owners should come prepared to share the status of their item and, ideally, a path to resolution. + For example, risk and task owners should come prepared to share the status of their item and, ideally, a path to resolution.

    @@ -924,7 +891,7 @@ Start with an answer.
    The worst question to ask is, "What did you do this week?" It invariably generates unnecessary, time-consuming dialogue from team members. Plus, you should already know what everyone on the team did during the week.

    - For example, risk and issue owners should come prepared to share the status of their item and, ideally, a path to resolution. + For example, risk and task owners should come prepared to share the status of their item and, ideally, a path to resolution.

    It is better to start with a "project answer", such as: "We are two weeks late", "We are at planned budget" or "We are 50% complete with the process model". Also if you can, start the meeting on a positive note, such as milestones that have been met or are ahead of schedule. This will make participants feel motivated to engage in the conversation.

    @@ -934,17 +901,17 @@
    Prepare an agenda (and keep to it)

    Be aware of the team’s productivity and time: try to keep meetings to one hour or less.

    -

    Use separate meetings to solve big issues or issues that aren’t important for the entire team.

    +

    Use separate meetings to solve big tasks or tasks that aren’t important for the entire team.

  • Roll call (5 min) Let everyone know who is in attendance before starting. This is important for remote team members who have dialled in and will save you time later.
    • -
  • New business issues (5 min) - You may have learned something during the week that affects the project. Share the news early in the meeting to help team members consider the issue as you walk through the project status session. Not every issue warrants spending time here, so keep discussions to a minimum.
    • +
  • New business tasks (5 min) + You may have learned something during the week that affects the project. Share the news early in the meeting to help team members consider the task as you walk through the project status session. Not every task warrants spending time here, so keep discussions to a minimum.
  • Project plan status review (20 min) Walk through your project plan and allow each team member to provide a brief status of assignments due this week and tasks planned for the next two weeks. You want to know whether tasks are on track and if any will miss their projected deadline. You also want to allow the team member to share any special considerations that might affect other tasks or members of the project. Carefully manage this part because some team members will want to pontificate and spend more time than is really needed. Remember, you’re the project manager.
  • Critical items (10 min) Upon completing the project status review session, summarize the critical items.
  • Q&A and discussion time (10 min) - Always give your team time to ask questions on issues that were not discussed. This gives you another opportunity to reinforce key points that you've picked up during the week or discovered during the meeting.
    • + Always give your team time to ask questions on tasks that were not discussed. This gives you another opportunity to reinforce key points that you've picked up during the week or discovered during the meeting.
  • Summary and follow-up items (5 min) Always wrap up with a project status summary and a list of action items dentified in the meeting to help move the project along.
  • Adjourn (5 min) @@ -956,7 +923,7 @@

    Follow every meeting with a recap email - As soon as the meeting is over, publish meeting minutes and distribute them along with the updated project schedule, issues/action item matrix, and any other appropriate documents. Try to use the same template throughout meetings and improve it continuously. + As soon as the meeting is over, publish meeting minutes and distribute them along with the updated project schedule, task/action item matrix, and any other appropriate documents. Try to use the same template throughout meetings and improve it continuously.

    • @@ -1002,15 +969,15 @@ Exercise 2
    - Delay to close an Issue + Delay to close an Task

    - Exercise: Try to create a graph with the monthly evolution of the 'Average delay to close' of Issues. + Exercise: Try to create a graph with the monthly evolution of the 'Average delay to close' of Tasks.

  • - Issues analysis + Tasks analysis
    • @@ -1064,7 +1031,7 @@ planner_project