Creating a Task

Project Tasks are the small parts of work that build up a discipline and thereafter a project, therefore projects must first exist before any can be created, see Creating A Project to get this done prior to creating project tasks.

Tasks can be as granular or generic as the organization prefers, the more granular they are the more detailed an operation Odin can provide. Tasks are easy to create and because we expect that the organization would use them in the 1000's with lost of similiar pieces of work Odin has been built with a range of powerful scaling tools. Most often tasks are related to Disciplines however this does not need to be done and the tasks can exist without a relation to a discipline directly under a project.

Creating a Task via Projects

To Create tasks as pieces of planned works, navigate to /projects, and follow the below steps

1. Select a project by clicking the checkbox and then clicking edit
2. Scroll down to the Disciplines and Tasks section and click Create
3. A sidebar will appear on the right, fill the details below and Save

Required filling

1. Task Name - used as a reference throughout Odin

Optional filling

1. Discipline - Used to store the quantities of this task in a cumulative sum on the discipline of the project. Also used to identify which resources can conduct this work via the discipline relationship. Start typing the name of the discipline and select it to assign it
2. Assigned - User or team that will be completing this task
3. Task Description - Description of the task, used throughout Odin to identify it differently from others that may have the same name
4. Proposed Amount - Quantity of works proposed to be apart of the task
5. Completed Amount - Quantity of works completed
6. Assignment Date - Date Assgined to the user/resource, recorded for reference and automatically populated when assigning a team or user
7. Completed Date - Date Completed by the user/resource, recorded for reference and automatically populated when work Completed Amount is filled in. If this box is checked and Completed Amount is empty, Odin will auto fill Completed Amount with Proposed Amount to default the task at 100% completion and save a double entry of information, values may then be adjusted if different to 100% completion. If this box is un-checked and was previously checked with a Completed Amount, Completed Amount will be reduced to 0 as most commonly a de-completion would indicate works was mistakenly reported. In the scenario where some work was complete but not all works, its ideal to clone this task and create two tasks for each portion, holding one for works completed at this point in time and the remainder with a proposed amount for the difference waiting to be updated by the resource.
8. Verified Date - Used to record a positive review of this item indicating all information reported is correct and true, only available once a task has been set to Completed or Invalid
9. Invalid Date - Used to record the de-scoping of this task. If this task is no longer required on the project, checking this box will de-scope it for scheduling but keep it assigned to the project as a reference if details of the projects are required at a later date. Checking this box will eliminate the Completed Date
10. Priority - Priority in which the tasks would ideal be completed
11. Task Notes - Planning or completion notes for this tasks
12. Address - Address of the task

Creating a Task via Projects (Smart Option A.)

If similiar tasks exists in the list, Odin can clone these to make tasks with the same attributes and work. Once cloned you may edit these to tweak them to their particular grades and disciplines. Odin provides the ability to clone many at once thereby reducing the effort to expand on a project once the initial tasks have been created.

1. Select the tasks to be cloned
2. Click Clone in the right sidebar
3. Tweak as desired (de-select any by un-checking its box on the left of its name in the main list)
4. Finally click Save

Creating a Task via Projects (Smart Option B.)

Tasks are usually multiplied across disciplines and as such Odin has a function that can clone tasks across to many disciplines after being created once. We call this spreading. In the simplest example, a brick wall may require 9 sqm of bricking but it may also require 9 sqm of rendering and 9 sqm of painting. To quickly and effectively create these tasks in Odin, simply create the first task for bricking and spread the task across to the other disciplines of rendering and painting. All the tasks details will be cloned over from bricking to a seperate task for rendering and a seperate task for painting. After the spread is complete these tasks are available for editing if required. This function combined with the clone process allows users to scale projects incredibly quickly. If push this one step further and Odin was to cater for 3 of these walls, the most efficient way to make the full scoped project would be to create the first bricking task, spread it across the next tasks in the chain (this gives one walls worth of work) and then select all the tasks for this wall and clone them, re-name the newly cloned tasks to wall to Wall 2 and change the other details that may differ (at this point all 3 tasks would be selected so changing the sqm to 12 would change it for all the newly created tasks) and repeat until 3 full walls are scoped. The inital task would take an initial few clicks to setup but every step there after is almost a one click process to create a matrix of work.

Spreading can only be conducted from Projects so to start snowballing these tasks, navigate to /projects, and follow the below steps

1. Select a project by clicking the checkbox and then clicking edit
2. Scroll down to the Disciplines and Tasks section and follow the steps in Creating a Task via Projects to create a task if an ideal task isn't available
3. Select the newly created or an ideal task by clicking its checkbox to the left of its name
4. In the right side bar that appears, click the button Spread (closer to the top of the screen)
5. Choose the disciplines to spread the task across by clicking the pencil next to Discipline, typing the discipline name and selecting the discipline when it appears. Many can be selected so don't hesitate to spread the task across as many disciplines as required
6. Click the Spread button one more time and they will all be created and pre-selected ready for tweaking
7. Finally click Save

Creating a Task via Updates

To Create a task as an update of spontaneous work creep, navigate to /updates, and follow the below steps

1. Select a project by clicking the pencil in the top left next to Project, type the project name selecting it once it appears
2. Scroll down to the Tasks tab section and click Create
3. A sidebar will appear on the right, fill the details below and Save

Required filling

1. Task Name - Used as a reference throughout Odin
2. Discipline - Used to store the quantities of this task in a cumulative sum on the discipline of the project. Also used to identify which resources can conduct this work via the discipline relationship. Only disciplines the user is capable of will appear in this list, to add a discipline to a resource see Creating A Resource

Optional filling

3. Task Notes - Planning or completion notes for this tasks
4. Address - Address of the task
5. Amount - Quantity of works completed
6. Completed Date - Date Completed by the user/resource, recorded for reference and automatically populated when work Completed Amount is filled in. If this box is checked and Completed Amount is empty, Odin will auto fill Completed Amount with Proposed Amount to default the task at 100% completion and save a double entry of information, values may then be adjusted if different to 100% completion. If this box is un-checked and was previously checked with a Completed Amount, Completed Amount will be reduced to 0 as most commonly a de-completion would indicate works was mistakenly reported. In the scenario where some work was complete but not all works, its ideal to clone this task and create two tasks for each portion, holding one for works completed at this point in time and the remainder with a proposed amount for the difference waiting to be updated by the resource.
7. Verified Date - Used to record a positive review of this item indicating all information reported is correct and true, only available once a task has been set to Completed or Invalid
8. Invalid Date - Used to record the de-scoping of this task. If this task is no longer required on the project, checking this box will de-scope it for scheduling but keep it assigned to the project as a reference if details of the projects are required at a later date. Checking this box will eliminate the Completed Date
9. Assigned - User or team that will be completing this task, defaults to the user creating the task
10. Task Description - Description of the task, used throughout Odin to identify it differently from others that may have the same name

Creating a Task via Updates (Smart Option A.)

If similiar tasks exists in the list, Odin can clone these to make tasks with the same attributes and work. Once cloned you may edit these to tweak them to their particular grades and disciplines.

1. Select the tasks to be cloned
2. Click Clone in the right sidebar
3. Tweak as desired
4. Finally click Save