Initial thoughts on Taskboard

[Cleve]

Hi Team Taskboard,

Firstly, I'm very impressed with Taskboard. You know its been
something I'm been passionate about for a long time and the solution
your have come up with is delicious, simple and useful and usable.

Below are some comments for potential improvements that you've aleady
thought about but here goes:

* Version number should be displayed somewhere so you know which
version to report bugs against
* Nice feature in products is to Send Issue which that always users to
report issues and then continue working
* When you add a column, you expect it to be added to the end and not
the start.
* No visual feedback on zoom level. I thought the taskboard had a bug
and was displaying task cards as one liners. Don't expect links (Zoom
In) to mask state. How about (Zoom 0,1,2,3) or something?
* Need a description when add tags to say that commas separate tags
and not white space
* Are you going to add a project level scope for taskboards? This
will be the first requirement, and then a release scope will quickly
follow. Or is this all done with tagging? Or a mixture between the
two? Interested to get your thinking on this.

Nice work.

Cheers,
Cleve

[Bartek Szopka]

Thanks for your comments Cleve.
Here are some of my thoughts.

> * Version number should be displayed somewhere so you know which
> version to report bugs against

To be honest version was quite 'fluid' for now but for sure we need to
handle it somehow.

> * Nice feature in products is to Send Issue which that always users to
> report issues and then continue working

The thing is that taskboard is not connected to any bug-tracker. You
can import issues by posting URL but that's all it does - parsing data
and adding cards. No relation between taskboard and bug-tracker is
stored.
I think taskboard is to manage development process. Bug-tracker itself
is for submitting bugs.

> * When you add a column, you expect it to be added to the end and not
> the start.

I agree that it's not very intuitive. Probably the only case it is a
bit useful is when you have so many columns that they don't fit on the
screen so if you add one in the end you don't see it. But this may
probably be handled by some auto-scrolling.

> * No visual feedback on zoom level.  I thought the taskboard had a bug
> and was displaying task cards as one liners.  Don't expect links (Zoom
> In) to mask state.  How about (Zoom 0,1,2,3) or something?

This zooming is quite temporary solution. I'm planning to turn it into
some slider like on google maps or something.

> * Need a description when add tags to say that commas separate tags
> and not white space

Some help tips are needed. Also for notes where you can use markdown syntax.

> * Are you going to add a project level scope for taskboards?  This
> will be the first requirement, and then a release scope will quickly
> follow.  Or is this all done with tagging?  Or a mixture between the
> two?  Interested to get your thinking on this.
>

We have plans to add some user-level access control, so one can
declare who can see and edit a taskboard.
We where not thinking yet about grouping taskboards in any way (tags
are for now only on card level). But for sure it will be useful if
Taskboard will be used across many projects.

Cheers,
Bartek

[Andrzej]

On 15 Maj, 10:34, Bartek Szopka <bartek.szo...@gmail.com> wrote:
>
> > * Are you going to add a project level scope for taskboards?  This
> > will be the first requirement, and then a release scope will quickly
> > follow.  Or is this all done with tagging?  Or a mixture between the
> > two?  Interested to get your thinking on this.
>
> We have plans to add some user-level access control, so one can
> declare who can see and edit a taskboard.
> We where not thinking yet about grouping taskboards in any way (tags
> are for now only on card level). But for sure it will be useful if
> Taskboard will be used across many projects.

Wrt project-level scope and grouping - it would be nice to have an
option to clone
an existing taskboard - meaning that a new empty one is created with
the same column
set as the base taskboard. This would enable users to easily add new
taskboards
for subsequent sprints for their projects.

Andrzej

[Bartek Szopka]

On Wed, Jun 24, 2009 at 12:01 PM, Andrzej<apuci...@gmail.com> wrote:
> Wrt project-level scope and grouping - it would be nice to have an
> option to clone an existing taskboard
>

This is quite commonly requested feature.
http://github.com/CognifideLabs/taskboard/issues#issue/6

It is quite possible that it will be soon implemented as teams that
use Taskboard for more that one iteration/sprint really need it.

Bartek