<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>aC forum: Milestones &amp; Checklists - Why Do We Need This?</title>
  <link>http://www.activecollab.com/forums/topic/2515/</link>
  <description>Recent posts on topic: Milestones &amp; Checklists - Why Do We Need This?</description>
  <dc:language>en-us</dc:language>
  <pubDate>Sat, 30 Aug 2008 08:09:06 CDT</pubDate>
  
  <item>
    <link>http://www.activecollab.com/forums/post/12194/#post12194</link>
    <guid>http://www.activecollab.com/forums/post/12194/#post12194</guid>
    <title>Post #24 by Brian</title>
    <dc:creator>Brian</dc:creator>
    <description><![CDATA[<p>Ilija, with all due respect, don't fall into the trap of building a product that is optimized for your personal workflow.  You know all the &quot;warts&quot; now and how to work around them so you may be minimizing the priority of what John and I have pointed out.</p>]]></description>
    <pubDate>Fri, 28 Mar 2008 09:41:29 CDT</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/12189/#post12189</link>
    <guid>http://www.activecollab.com/forums/post/12189/#post12189</guid>
    <title>Post #23 by Powerlet</title>
    <dc:creator>Powerlet</dc:creator>
    <description><![CDATA[<p>Ilija you have a wonderful product.  I like aC.  However, I would like to tell others &quot;I love aC&quot;.<br />
<br />
We consciously avoided the Corp version to keep things simple.  Money was not the issue, we wanted a &quot;basecamp&quot; like product were they advertise &quot;we offer less features than the competition&quot;.  After 23 years of engineering I am convinced most people can design a complicated system; few can design a simple system that performs.  <br />
<br />
That said, add me to the list of those who assumed tickets were the traditional &quot;trouble tickets&quot;, not an alias for &quot;tasks&quot; or &quot;checklists&quot;.  When your pinched for time it is easy to miss.  So for marketing purposes I would look at this hard Ilija, most likely this issue will not go away for future customers.<br />
<br />
Currently we use the small biz version like this: Projects &gt; Milestones &gt; Checklists &gt; Tasks<br />
<br />
But as pointed out in prior posts, this is flawed.  For what it is worth here is how I would recommend fixing the warts:<br />
<br />
First, the small biz product needs to stand on it's own two feet, no compromise.  This means &quot;checklists&quot; need people and deadline assignments. When selecting the checklist tab they need to be sorted by milestones.  Printouts need to show the full path and be sorted by project, milestone, checklist and task.  Small Biz needs the calender.  A calender is not an option, it is essential to complete the small biz product. <br />
<br />
Second, the Corp version should have simply &quot;more&quot; for those who need it.  I would suggest:<br />
1. Projects &gt; Milestones&gt; Checklists&gt; Tasks &gt; Sub-Tasks (sub-tasks &amp; task comments would be worth the price of admission)<br />
2. Traditional &quot;trouble tickets&quot; (again well worth the price if you need this functionality)<br />
3. Time Tracking<br />
4. Pages<br />
<br />
To clarify: for marketing, upgrades, user interface consistency, and development sake I would only add features to the same path to differentiate small-biz from Corp.  I would drop having two paths (checklists for small-biz and tickets for corp ) as it is today.<br />
<br />
</p>]]></description>
    <pubDate>Fri, 28 Mar 2008 00:29:41 CDT</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11938/#post11938</link>
    <guid>http://www.activecollab.com/forums/post/11938/#post11938</guid>
    <title>Post #22 by Brian</title>
    <dc:creator>Brian</dc:creator>
    <description><![CDATA[<p>Can't argue with that wisdom. ;-)</p>]]></description>
    <pubDate>Mon, 25 Feb 2008 11:14:46 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11934/#post11934</link>
    <guid>http://www.activecollab.com/forums/post/11934/#post11934</guid>
    <title>Post #21 by Ilija Studen</title>
    <dc:creator>Ilija Studen</dc:creator>
    <description><![CDATA[<p><div class="postQuote"><blockquote><div class="quoteAuthor">Brian:</div>Ilija, my sense is that you don't see this issue as a priority but I think Brandon's comments point out that the longer you wait to address it, the more difficult it is going to be for you to make any changes. And without those changes, you're constraining new customer adoption.</blockquote></div><br />
<br />
Next version of activeCollab is frozen so no new features or major adjustments will be made until it's launched. It's just one of the methods to make sure that software is shipped - as soon as development hit &quot;feature freeze&quot; no new features or big system changes is being introduced. Every new feature added after that is potential treat and could make testing more complicated and delay the release.<br />
<br />
When done we'll consider this change to be introduce in one of the later release, but currently our priority is to ship v1.1. </p>]]></description>
    <pubDate>Mon, 25 Feb 2008 09:40:20 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11933/#post11933</link>
    <guid>http://www.activecollab.com/forums/post/11933/#post11933</guid>
    <title>Post #20 by Brian</title>
    <dc:creator>Brian</dc:creator>
    <description><![CDATA[<p>Good comments Brandon.  It sounds like you are using the classic interpretation of Tickets. ;-)  However, I'm getting the impression that what most users are doing, is using Tickets the way you are using Checklists. <br />
<br />
In fact, for your situation, if Tickets was renamed to Checklists and Checklists was renamed to Tickets, wouldn't that give you everything you're looking for? <br />
<br />
Ilija, my sense is that you don't see this issue as a priority but I think Brandon's comments point out that the longer you wait to address it, the more difficult it is going to be for you to make any changes. And without those changes, you're constraining new customer adoption.</p>]]></description>
    <pubDate>Mon, 25 Feb 2008 09:21:07 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11916/#post11916</link>
    <guid>http://www.activecollab.com/forums/post/11916/#post11916</guid>
    <title>Post #19 by cbtrussell</title>
    <dc:creator>cbtrussell</dc:creator>
    <description><![CDATA[<p>I'll chime in as someone who does NOT want to see checklists eliminated.<br />
<br />
We are just starting to actively utilize aC for our projects. We have a well defined project process and use the same steps for every project.<br />
<br />
Milestones represent phases of the project (usually only 4 or 5)<br />
<br />
Checklists represent groups of tasks required by the project process<br />
 - each checklist has anywhere from 2-10 subtasks that are assigned to project participants with due dates as appropriate<br />
<br />
Tickets are used to track issues/requests that are NOT explicitly addressed by the process - in other words, anything that comes up outside of the process is documented in a ticket and then assigned to a participant for resolution.<br />
<br />
So from our perspective, it is critical that the checklist function remain in aC, and be separate from tickets. But I would like to be able to comments on checklist tasks and also be able to attach time to them.<br />
<br />
Brandon</p>]]></description>
    <pubDate>Sat, 23 Feb 2008 20:21:53 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11907/#post11907</link>
    <guid>http://www.activecollab.com/forums/post/11907/#post11907</guid>
    <title>Post #18 by Brian</title>
    <dc:creator>Brian</dc:creator>
    <description><![CDATA[<p>Yes, I hope we hear from others on this...  <br />
<br />
BTW, In the meantime, here's what I did:<br />
<br />
1. Used the tip previously posted on hiding the time tab but instead I hid the Checklists and Pages tab from everyone.<br />
2. I hid the Time tab from the client view using the tip.  We don't have plans to use it but I thought I might want to play with it.<br />
3. Changed the text displayed on the Tickets tab for everyone to &quot;Tasks (Tickets)&quot;.  I'm still going to have to explain this but at least it will cause users to ask questions instead of thinking it's a Trouble Ticket.<br />
<br />
Took me about 10 minutes do this.<br />
<br />
</p>]]></description>
    <pubDate>Sat, 23 Feb 2008 13:30:20 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11904/#post11904</link>
    <guid>http://www.activecollab.com/forums/post/11904/#post11904</guid>
    <title>Post #17 by Sebastian Tänzer</title>
    <dc:creator>Sebastian Tänzer</dc:creator>
    <description><![CDATA[<p>Brian,<br />
<br />
I don't see any use in checklists either. Never used them.<br />
A ticket with subtasks has way more functions and does the same.<br />
<br />
But perhaps someone out there is using checklists for something useful? <br />
Feedback from the community on this would be great!<br />
<br />
I'm all in for the changes you supposed. It would make the whole system a lot easier.<br />
When we introduced aC 2 months ago about the only question I received from our team was about tickets (i.e. &quot;Where does the customer send the email to to open a ticket&quot; and so on...) - most of these because the term &quot;ticket&quot; was known from existing support ticket systems. One can't reinvent the whole project management system and tell the customers &quot;Well, from now on we'll redefine tasks as tickets ...&quot;. Just does not work.<br />
<br />
</p>]]></description>
    <pubDate>Sat, 23 Feb 2008 06:55:17 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11889/#post11889</link>
    <guid>http://www.activecollab.com/forums/post/11889/#post11889</guid>
    <title>Post #16 by Brian</title>
    <dc:creator>Brian</dc:creator>
    <description><![CDATA[<p>Good comments Andrew...  Couldn't you use Tickets to accomplish the very same operating model?  <br />
<br />
Well, we've (reluctantly) made the decision to upgrade to the Corp edition.  Frankly, it was a close call with the alternative being to pay one of my programmers to tweak Webcollab or PHPCollab to meet our needs exactly. But with comments like Sebastians, we've decided to try 30 days and a couple projects to see if we can fall in love as well ;-)<br />
<br />
I do hope to see a further momentum on the need to change this Tickets thing.  IMHO, this is a totally confusing misnomer...<br />
<br />
One more time:<br />
1. Change Tickets to Tasks<br />
2. Change Tasks to Subtasks<br />
3. Eliminate Checklists (or move it to Corp if there is some reason to keep it that I'm not understanding and change tasks to subtasks).<br />
<br />
Make that your small biz edition, raise price to $249 or even $299<br />
<br />
Corp edition adds Time, Pages, Calendar priced at $399<br />
<br />
(You might also add a free version that is the Small Biz for 1 or 2 projects).<br />
<br />
==&gt; Happier, less confused users.  And therefore more users, more customers, more funds for development.<br />
<br />
<br />
<br />
<br />
</p>]]></description>
    <pubDate>Fri, 22 Feb 2008 09:33:34 CST</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/11886/#post11886</link>
    <guid>http://www.activecollab.com/forums/post/11886/#post11886</guid>
    <title>Post #15 by andrewCharron</title>
    <dc:creator>andrewCharron</dc:creator>
    <description><![CDATA[<p>Something everyone needs to remember is that not everyone uses aC the same. Something which you may have a dire need for, everyone else may not want or need, and thusmay not be as needed as you think.<br />
<br />
For example, I have no use for tickets, yet we currently use the corp version. The way we have it set up is that milestones are set as milestones and assigned to project leader. Easch milestones have parts that need to be finished, and thus checklists. In all reality, we dont need a checklist to be assigned to anyone (Although it might be useful). Inside the checklists are tasks that need to be finished in order to complete the checklist, and each is assigned to whoever is responsable.<br />
<br />
However, we can see this from the other side as well. Ilija may need to realize that not everyone can use the software the way it is written, and some features that he doesnt know about may be in desperate need of being added.</p>]]></description>
    <pubDate>Fri, 22 Feb 2008 07:58:36 CST</pubDate>
  </item>
</channel>
</rss>