Table of contents:
1.1 Import & Export file structure
1.3.1 Add to existing - Import
1.3.2 Replace Everything - Import
2. Checklist template for organizations
1. Single project checklist
Checklists which are used in a single project
1.1 Import & export file structure
An example file (.xlsx) might look like this:
Headers:
- Index *- This field determines the location of the element in the structure. Each element(except root) must have a parent. For example, if we want to have 1.1.2 node we need to create node 1.1 and 1. The node at the end of the tree is treated as a checklist item. In this example nodes 1.1.1, 1.1.2, 1.2.1 and 1.2.2 are items.
- Name *- Name of the checklist node.
- Description - Detailed description of checklist node.
- Due date - Date when the checklist item should be completed. The format must be yyyy-mm-dd.
- Hours planned - Numbers of hours that we assume for checklist item.
- Hours spent - Numbers of hours that currently spent on checklist item.
- Progress - Percentage value of checklist item completion. (the value must be whole number)
* - Required fields


1.2 Export



1.3. Import




Please see 1.3.1 for Add to existing, and 1.3.2 for Replace everything.


1.3.1 Add to existing - Import
For example lets say you have a project where the current checklist export looks like this:


Here 1.2, 1.2.1, and 1.2.2 are added, and 1.1.2 is updated with a new name and new data.
Since we are using "Add to existing" for this import, only the new fields will be added (marked in green) into the checklists. The existing checklists will not be changed.

1.3.2 Replace everything - Import
For example lets say you have a project where the current checklist export looks like this:



2. Checklist template for organizations
Checklist templates allow you to create a checklist structure and add it into your organization, and easily use in all projects within the organization.
2.1 File structure
An example file (.xlsx ) might look like this:
Headers:
- Index *- This field determines the location of the element in the structure. Each element(except root) must have a parent. For example, if we want to have 1.1.2 node we need to create node 1.1 and 1. The node at the end of the tree is treated as a checklist item. In this example nodes 1.1.1, 1.1.2, 1.2.1 and 1.2.2 are items.
- en-US *- Name of the element
- Description en-US - Description
- Due date delay in days - The amount of days after set start date this element / chapter should be completed.
- Hours Planned - How many hours are planned for this element
- Relevant URL - Any URL related to the element can be added here and is easily accessible by other members viewing this checklist.
* - Required fields
2.2 Import
To create and import a new checklist template you must be an administrator for your organization.
1. Go to the organizational panel
2. Select "Checklists"
3. Type a name for the template and click "Add template".
4. Click the "Import" button by the new template you added and upload your .xlsx file.
5. Your template is now available for every project in your organization.
To use the template in a project follow these steps:
1. Create a new project within the organization, or find an existing project without any checklists which is part of the organization.
2. Click "Enable checklists".
3. Select the template you have imported into the organization, and click "Enable checklists".
This is also where you add a start date of your project, if you used the "Due date delay in days" field in your template.
4. The checklist structure is now activated in the project. We can see that the data from the template is there, and the due date is automatically populated based on the start date.
This checklist element had a "4" on "Due date delay in days". The start date of the checklist was set to 31.01.2020. Therefore the final due date is 03.02.2020.
2.3 Export
To export your template, go back to where you created the template and click on the "Export" button.
Comments
0 comments
Please sign in to leave a comment.