<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Project Trackr Development Log &#187; Tasks</title>
	<atom:link href="http://logbook.projecttrackr.com/category/section/tasks/feed/" rel="self" type="application/rss+xml" />
	<link>http://logbook.projecttrackr.com</link>
	<description>Building a better web based project management solution</description>
	<lastBuildDate>Mon, 15 Mar 2010 15:33:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Exploring data input options for tasks</title>
		<link>http://logbook.projecttrackr.com/section/tasks/exploring-data-input-options-for-tasks/</link>
		<comments>http://logbook.projecttrackr.com/section/tasks/exploring-data-input-options-for-tasks/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 12:44:02 +0000</pubDate>
		<dc:creator>Damian Jakusz-Gostomski</dc:creator>
				<category><![CDATA[Tasks]]></category>

		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=276</guid>
		<description><![CDATA[Although I am still in the process of requirement gathering, I know that tasks will definately be a part of the final system, as a large part of project management is knowing what needs to get done, which is represented as a set of tasks.
Therefore, it is important that the method for entering tasks is [...]]]></description>
			<content:encoded><![CDATA[<p>Although I am still in the process of requirement gathering, I know that tasks will definately be a part of the final system, as a large part of project management is knowing what needs to get done, which is represented as a set of tasks.</p>
<p>Therefore, it is important that the method for entering tasks is as simple and streamlined as possible. This post will explore some of the possible ways to allow data input for the tasks.</p>
<p>Before we can begin, we need to plan what items we <strong>need</strong> and what items are <strong>nice to have</strong> when adding tasks to the system.</p>
<p><strong>Must have:</strong></p>
<ul>
<li>A name for the list of tasks</li>
<li>One or more tasks</li>
</ul>
<p><strong>Optional:</strong></p>
<ul>
<li>Description</li>
<li>A user/group to assign the task to</li>
<li>A date the task must be completed by</li>
<li>Any links to other tasks, milestones, tickets etc</li>
</ul>
<p><span id="more-276"></span></p>
<p>So we need to have at least 2 fields, one for the name of the list and one for the task itself. The problem then is what do we do when we need more then one task (which is the case most of the time). We can have a preset number of fields for the tasks (eg 10) but then this will either not be enough or it will be more then we need and will be additional clutter.</p>
<p>Another option is to split it into 2 phases.</p>
<ol>
<li>The user creates a list (with optional description) and submits that form</li>
<li>They&#8217;re then taken to another page where they add an item to that list</li>
<li>When that form is submitted, the item is added, the page is reloaded and they can add a new item</li>
</ol>
<p>The problem with this, is it may take several pages to create a basic list. Although this may be the easiest method to implement, it&#8217;s probably the worst from the users point of view.</p>
<p>Another option is to just have a textarea where each line represents one task. This allows them to enter any number of tasks, all in a single form submission. The problem with this method is it can get very messy if we want to add meta data to the tasks, such as assigning it to a user, linking it to another item or setting a due date.</p>
<p>Another issue is do we ask for all the required information first and then get any optional information afterwards. The benefit of this is if they just want to give the required information, then they just need to worry about the first part of the form. The downside is parts may lose context, such as the description of the list. It&#8217;s an optional field, but if you want to fill it in, it&#8217;s best to do so at the start, after giving the list a name. Although this may be unnecessary form clutter for most users. A 3rd option is to have this after the list name field, but to have it hidden unless you want it, in which case it will appear after clicking a link.</p>
<p>Another possibility is to use AJAX to submit the form dynamically. This means we can have the form for one task, and it will be submitted and appended to the list under the form. This is probably the most streamlined method possible, as it allows us to also easily include meta data if we want, or we can easily just add a task, hit enter, add another task etc</p>
<p>I&#8217;ll initially implement the last method suggested, and get some user feedback on it before implementing it fully into the project, but in the meantime, if anyone has any thoughts or comments on how to do it better, then post  in the comments below.</p>
]]></content:encoded>
			<wfw:commentRss>http://logbook.projecttrackr.com/section/tasks/exploring-data-input-options-for-tasks/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Tasks Intro</title>
		<link>http://logbook.projecttrackr.com/section/tasks/tasks-intro/</link>
		<comments>http://logbook.projecttrackr.com/section/tasks/tasks-intro/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 19:20:24 +0000</pubDate>
		<dc:creator>Damian Jakusz-Gostomski</dc:creator>
				<category><![CDATA[Tasks]]></category>
		<category><![CDATA[intro]]></category>

		<guid isPermaLink="false">http://logbook.projecttrackr.com/?p=153</guid>
		<description><![CDATA[Tasks are all about tracking what&#8217;s been done and what needs to be done.
Now that you know what the project is about, and you&#8217;re up to date with all the latest information, you need to know what to do. This is where tasks come in. Tasks are essentially TODO lists, where you can:

Create, edit, delete [...]]]></description>
			<content:encoded><![CDATA[<p>Tasks are all about tracking what&#8217;s been done and what needs to be done.</p>
<p>Now that you know what the project is about, and you&#8217;re up to date with all the latest information, you need to know what to do. This is where tasks come in. Tasks are essentially TODO lists, where you can:</p>
<ul>
<li>Create, edit, delete and complete tasks</li>
<li>Assign tasks to users and see tasks assigned to you</li>
<li>Create nested lists where each sub lists is a large task, which needs to be broken into sub pieces to be tackled efficiently.</li>
<li>Un-complete tasks in case they weren&#8217;t actually completed</li>
<li>View when a task and list was completed and by whom</li>
<li>Set priorities for tasks,  so you can see at a glance what needs to be done as soon as possible</li>
<li>Categorise lists of tasks, such as the type of work involved, the stage of the project etc</li>
<li>Comment on tasks</li>
<li>Track time spent on a task</li>
<li>Search your tasks, completed and pending</li>
</ul>
<p>You will also be able to link tasks to other resources, so if a task is created in response to a ticket, you can see the ticket alongside the task, or if the task involves working on a file, the file can be linked to the task, so you have all the required resources rto hand when you begin working on a task.</p>
]]></content:encoded>
			<wfw:commentRss>http://logbook.projecttrackr.com/section/tasks/tasks-intro/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
