Task Lists

by Nate on February 1, 2010

As some of you have already noticed, we released a new version of Zen last night! This version has quite a few changes, but the most significant is the addition of task lists inside of stories. Here’s a quick tour to give you an idea of how to use the feature.

You can add tasks to a story when you create it by clicking the Edit Tasks button on the Add Stories panel. From the board, you can add add tasks to an existing story by clicking the new tasks button on the story toolbar:

tasks-toolbar

You can add tasks to a story from the story screen as well. Once a story has tasks, you will see an additional section on the story card, similar to the one shown for file attachments. This summary indicates both the total number of tasks and the number that have been completed, along with a rough completion percentage:

tasks-collapsed

Bear in mind that if all of the tasks are not equal in size, this completion percentage isn’t a perfect indicator of how much of the story is complete. Still, it can be helpful to check the completion status of a story at a quick glance. To view the specific tasks, click the summary, and the card will fold out:

tasks-expanded

As you can see, this story describes the development of a simple e-commerce payment page. You can re-order tasks by grabbing a task’s drag handle (on the left) and moving it into the position you want. If you decide you don’t want a task anymore, the button at the right will delete it from the story. Unlike stories, there is no process for tasks to travel through – they’re either finished or not. To mark a task as finished, click its checkbox. From then on, when the story’s task list is expanded, Zen will show a description of who finished the task and when:

tasks-checked

To collapse the task list again, click Hide. In this case, since we checked off a task, the story’s task summary will be updated to reflect the new status:

tasks-collapsed-2

So, that’s a quick tour of tasks. While you should obviously feel free to use the feature however works best for you, remember that tasks typically should not line up with the columns on your board. For example, if you have a phase on your board called Test, you probably shouldn’t add a task called “test this story.” However, you might want to add multiple tasks related to testing, like “regression testing” and “cross-browser UI testing”, both of which are expected to be finished within the Test phase.

The easiest way to think about it is that your story is a goal that you want to achieve, the tasks are steps toward that specific goal, and your phases are the milestones that all stories must move through in order to reach completion.

Like I said, tasks are the biggest addition, but certainly not the only one. We’ve made quite a few bug fixes and usability tweaks:

  1. You can now set priority, deadline, and owner when creating a story, instead of having to go to the story screen to set them.
  2. Switched to MarkdownSharp for Markdown rendering, which means we’re now running on the same flavor of Markdown as used by Github and Stack Overflow.
  3. URLs within Markdown-enabled fields are now automatically turned into hyperlinks.
  4. Added the ability to link to stories by entering the story number in any Markdown-enabled field; for example: entering #123 will create a link to story 123.
  5. Removed the hotkeys for expanding the backlog and archive which were interfering with some users’ keyboard-fu. (We have plans to add a lot more keyboard shortcuts to the app, so they’ll be back eventually.)
  6. The magnifying glass on stories is a normal link again, instead of being controlled by JavaScript. This means you can right-click and copy the URL for a story, or middle-click to open it in a new tab.
  7. The problem where some projects’ cycle time charts were out of chronological order has been fixed.
  8. The problem where some projects’ efficiency ratings were above 100% has been fixed. (Don’t worry, you’re still awesome, just not 5000% awesome! :)
  9. Performance charts now respect individual users’ date format selection.
  10. We’re no longer relying on HTTP verbs other than GET/POST, which should solve problems with overly-aggressive corporate firewalls.
  11. Several other minor visual tweaks.

As always, if you have any questions or feedback, we’re all ears!

a79424aa4eb647944b723b43594e4b93
  • http://twitter.com/jnewland Jesse Newland

    No API features? Sad panda :(

    No pressure, just wanted to give you a hard time. The task lists looks awesome :)

  • http://twitter.com/DannyDouglass Danny Douglass

    Love the tasks feature – thanks!

  • http://twitter.com/hellogerard hellogerard

    My two favorite changes of this release:

    1) Task Lists
    2) Removal of hot keys – I get my Ctrl-Shift-Arrow back!

  • http://www.designinginteractive.com/ Dave Goerlich

    This is excellent! We will use the task lists quite a bit I'm sure. Matter of fact, I'm going to go back through our active cards right now and put them to use!

    Oh, and thanks for fixing the keyboard shortcuts. I'll admit to having been annoyed by them more than a couple times.

  • http://twitter.com/afifraza Afif Raza

    Hi Nate,
    First off, great work., my question may not perhaps relate to what your tool is intended to be., but I am curious. How does your software tie into the dynamics of the delivery of software once it has been pushed to production? As in one may find anomalies against some stories., which results in assigning defects next to them? Do you recommend on using a separate bug tracking software?

    Afif

  • Steve Campbell

    I'm not Nate, but I can say that on our team we have discussed this quite a bit and gone back and forth on deciding how to represent defects on the board. This is what works for us today:

    Defects are entered into our bug tracking software. They are triaged, and if we decide to do a fix then we create a new story on the board, in orange. This new story is then worked like any other. We still track the issue in the bug tracking software. This is duplicate work, but we decided that we needed the visibility of the board, but also wanted the audit trail of comments in the bug tracker software.

    Other defects discovered during testing (prior to production) are not tracked as stories on the board, although they may cause a story to be blocked.

  • http://twitter.com/ponderings DeanG

    >> [Task Percentage] can be helpful to check the completion status of a story at a quick glance

    Here's a vote to suggest it's more of a distraction. The # of # count qualifies this, and the % brings to mind 80/20 cliches and the failures of status by percentage.

    Please consider Sparklines if you think the counts need a supplemental view.

  • eugeneware

    Great job. I just signed up for the $99/month plan :-)

    However, I just noticed that if two people are viewing the kanban board at the same time and one makes a change… it DOESN'T CHANGE on the other person screens.

    I'm sure it's high on the todo list, but as a team collaboration tool, it's pretty important that this gets dealt with soon wouldn't you agree?

    This is something that Pivotal Tracker does really well using a “long poll” ajax script.

    Beautiful product, really nice.

Previous post:

Next post: