{"id":2413,"date":"2015-10-14T12:39:27","date_gmt":"2015-10-14T12:39:27","guid":{"rendered":"https:\/\/twproject.com\/support\/?page_id=2413"},"modified":"2024-08-26T14:04:36","modified_gmt":"2024-08-26T14:04:36","slug":"issues","status":"publish","type":"page","link":"https:\/\/twproject.com\/support\/using-twproject\/issues\/","title":{"rendered":"ToDo – project’s micro activity"},"content":{"rendered":"

What is a ToDo? It\u2019s something smaller, less relevant, more agile than a project.
\nTo-dos, remember to, bugs, notes, suggestion, tickets, prospects, opportunities etc. are perfect examples of\u00a0what Twproject call “ToDo”.<\/p>\n

Each ToDo can be assigned to a user, have a deadline, a priority, and a status (e.g., open, in progress, completed). In Twproject, ToDos are always linked to a project or a phase. At the top banner of the homepage, you can always see overdue ToDos, those due today, or upcoming ones.<\/p>\n

To learn how to manage them effectively, you can watch the\u00a0video tutorial<\/a>, or follow the instructions below:<\/p>\n

ToDo are a perfect solution for\u00a0avoiding to create over complex tree structures; when your project\u00a0has many phases, you could stop creating new phases, and start adding ToDos.<\/p>\n

ToDo are by far simpler to manage than projects, so use them whenever you can. thanks to the WBS you will be always aware of how many of them you have in the tree nodes and you will have a red alert in case of something expired.<\/p>\n

\"\"<\/p>\n

In order to create a “ToDo” go to one of your projects and add one.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Just insert the description (project is assigned automatically) and save it; quite simple!
\nHave a look to the main information on ToDo:<\/p>\n

Title:<\/strong>\u00a0Is a short sentence that helps to identify your activity synthetically.\u00a0It\u2019s not mandatory, you can only choose to fill the description field if it\u2019s more functional for you.
\nIt will be full-text indexed, so will be easy to retrieve ToDo.<\/p>\n

Description<\/strong>: Is the “body” of your activity. Write whatever you want, there is no limit in length. The description\u00a0will be full-text indexed, so will be easy to retrieve ToDo.<\/p>\n

Project<\/strong>:\u00a0 This is a key information. Every ToDo refers to a project, so that work done, alerts, reminders, security are inherited from the project.<\/p>\n

Assigned to<\/strong>: Is the resource responsible to perform the activities described \u00a0The assigned resource must be involved on the project too, so if you select a resource non yet assigned on the project, a new assignment will be created automatically (using project defaults). A ToDo can be “passed” from a resource to another; every change will be recorded on the ToDo history.<\/p>\n

Severity<\/strong>:\u00a0Key\u00a0information.\u00a0Severity should impact on the order of execution; blocking ToDos must be resolved before\u00a0critical or low ones. Severity is hard-coded and cannot be changed. By default severity is used for\u00a0sorting ToDo.<\/p>\n

Status<\/strong>: Key information. Status is used for managing a resolution flow. The simpler flows are open -> close or open -> paused -> test -> close. You can modify\u00a0statuses or create new ones. Statuses can behave as “open” (need activity) or as “closed” (do not need activity). Every status change is recorded on ToDo history.<\/p>\n

Type (optionable)<\/strong>: Could be used to classify your ToDo.<\/p>\n

Impact (optionable)<\/strong>: Reflects the impact that your ToDo will have\u00a0on the project.<\/p>\n

Do on<\/strong>: This is the date the ToDo should be done. If the ToDo has an estimated work, from the point of view of the operator work load, it is supposed to be done on that date.<\/p>\n

Estimated<\/strong> work<\/strong>: Is an estimation on hours of the work necessary to close the ToDo. Usually an ToDo should be small enough to be resolved within a working day, but this is\u00a0absolutely not\u00a0mandatory.<\/p>\n

Tag<\/strong>: ToDos can be tagged. Tags are defined on-the-fly and can be reused once defined.<\/p>\n

Attachments<\/strong>: You can attach as many files you need on every ToDo. Drag and Drop your files on the ToDo row.<\/p>\n

Comments<\/strong>: ToDo can be commented.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

Click on the ToDo row to edit it.<\/p>\n

You can edit multiple lines at once and save all with one click; ctrl+enter will save the current\u00a0row.<\/p>\n

ToDo descriptions and notes both support clickable links and Twproject smart link.<\/p>\n

ToDo list is sortable by using drag&drop, but consider the “severity”….<\/p>\n

If you have to insert several ToDo for the same project and the same assignee consider to\u00a0use the\u00a0\u00a0“copy” button \"\", to\u00a0speed-up the insert.<\/p>\n

You can\u00a0register work done on every ToDo you are assigned to (or on the ToDos related to a project where you are assigned to as well); the work recorded will always be collected on the related project and will be “linked” to the originating ToDo.<\/p>\n

ToDo are extremely flexible, and can be used for different purposes; to access the full spectrum of functionality open the complete editor using the edit icon:<\/p>\n

\"\"<\/p>\n

Up to 8 custom fields <\/a>can be created on a ToDo.<\/p>\n

Sometimes what has been inserted as a small ToDo generates a new project.
\nFor instance one of your customers require a new feature on an existing product, and after the analysis you discovered that this requires several days of work with several resources involved.\u00a0In this case you could “upgrade” the ToDo to project. The originating ToDo will be closed and a new project (as child of the current one) will be created.<\/p>\n

Another aspect of ToDo that increases usability is related to security<\/strong>. Permissions required to insert ToDo are distinct from permissions on project, so for instance you can create security profiles with read-only permission on project and creation permission on ToDos: we can call this set of permissions \u201ccustomer\u201d and create an ad-hoc role. Assigning customers with this role will allow them to insert ToDos right at developer\u2019s hand; it also facilitates creation of a \u201cbacklog\u201d that is very common on agile methodologies.<\/p>\n

 <\/p>\n

Re-scheduling ToDos<\/h3>\n

\"screen1253\"<\/p>\n

A smart Scrum team leader that is using Twproject remarked the following: suppose that you are a developer and are assigned on a set of ToDos, on which you do your development and record development time spent. You did with the team the initial evaluation of needed development time, and suppose for a particular ToDo you decided to put 10 hours.<\/p>\n

You recorded time elapsed, but as happens in real life all the time, you have to reschedule some of the ToDos. Now the users remarked that it is quite cumbersome to reason on the base of estimated duration – worklog done, because all you are actually focused on is time remaining to close the ToDo.<\/p>\n

\"screen1254\"So, here is the change: by clicking on worklog done, a time remaining panel appears, and its editable right there.<\/p>\n

This little practical change can make a difference; think when you planned 34 hours, and have done 27:30, how many hours to go, will it suffice.. I don’t want spend time on that: just let me reschedule that.<\/p>\n

If you want to link directly to an ToDo via a URL, use:\r\nhttp:\/\/[your root]\/issue\/X<\/strong> \r\nwhere X is the ID of the ToDo.<\/pre>\n
ToDos are a perfect solution for Agile approach to project management and for planning your work. See how on the following\u00a0sections.<\/p>\n
Repeat ToDos<\/h3>\n
Recurring Todos are micro activities that happen over and over again, on a regular basis in a project. As a worker it’s common to have regularly scheduled reporting intervals (Daily, Weekly or Monthly).\"\"
\nChoosing “Repeat” button you will open a dialog box with possible setting repetition for any dates and frequency you want rather than being limited to daily\/weekly\/monthly options. Selecting how many times you want the ToDo to repeat.
\nIn the ToDo list you’ll see the nearest recurrence ToDo scheduled, you can undestand that it has recurrence thanks to an icon on the right of date “Do on”
\nYou can check the recurrence settings or change it by clicking on the three dots and choosing the “Repeat” item in the menu. You can filter for this type of Todo by choosing in the filter section Dates the botton “Recurrent Todo”.<\/p>\n
ToDo list and Gantt chart viewable together<\/h2>\n
We have introduced a new view to simplify meetings and allow working on ToDos directly from the Gantt. Check out this dedicated video<\/a>.<\/p>\n
The extended list\u00a0 ToDos list in a side tab to the Project Gantt<\/h3>\n
\n
\"Show<\/figure>\n<\/div>\n
Choosing the “ToDo list” button in the navigation bar will open a second navigation window, which can be displayed alongside the current one. This new window will show the extended list of ToDos related to the phase you are currently in.<\/p>\n
By clicking on the various phases within the Gantt,\u00a0the list will update showing the ToDo\u2019s for each selected phase<\/strong>.<\/p>\n
\"ToDo<\/figure>\n
By default, the list shows open ToDos for active phases and closed ToDos for completed phases. But this display can of course be changed using filters. For example, if you also want to see closed tasks for a phase that is still in progress, just set the filter \u2018Status\u2019 to\u00a0all\u00a0<\/em>so that you see the complete list of open, closed, or else, ToDos.<\/p>\n
From this window you can also act on the ToDo list as usual, adding items to the list, changing assignments, dates, priority, etc.<\/p>\n
The ToDo summary for each phase while consulting the Gantt<\/h3>\n
\n
\"Show<\/figure>\n<\/div>\n
By clicking on this icon in the horizontal function bar of the Gantt, and selecting \u2018ToDo data\u2019, it will be possible to display a summary of the ToDo status for each individual project phase in a new column of our Gantt.<\/p>\n
The overview will show\u00a0a column with a summary of the ToDos (open \u2013 closed \u2013 total) for each individual phase<\/strong>. And all this will be visible without having to open additional pages.<\/p>\n
\"ToDo<\/figure>\n
This new way of reading the Gantt and ToDo summary together is useful to see at a glance where delays are accumulating and\/or where there is the greatest active workload.<\/p>\n
<\/h2>\n\n\n