Assignee names

23 views
Skip to first unread message

vhvhvh...@gmail.com

unread,
Mar 10, 2015, 12:01:52 AM3/10/15
to kanb...@googlegroups.com
It would be really cool if we could see Assignee names on the cards.

jel...@gmail.com

unread,
Mar 10, 2015, 2:44:21 AM3/10/15
to kanb...@googlegroups.com, vhvhvh...@gmail.com
What you can do currently is to show the user picture on the task.
Do you need to show the assignee name? Where would you put it? It does not fit into the header... Maybe between header and body? Or bottom of the task?
Or would it be enough to show it in title when hovering the task?
Any idea where would it look ok? Not really sure.

Venkatesh Hegde

unread,
Mar 11, 2015, 1:13:26 AM3/11/15
to jel...@gmail.com, kanb...@googlegroups.com

Currently i have been using Initials: task

it is very helpful to visually see who is assigned to what.

I believe this tool has potential to be one of the best. Great job !

I have been trying to triangulate workflow,  task and project management.

Workflow view helps in knowing that tasks have been planned and using color coding one can indicate that tasks are stuck.

From an individual perspective,  tasks make more sense.  Filter feature does that for you.

Now when it comes to dates,  this tool is lacking to mark tasks as done. Or to put in estimates as number of days,  or export as csv file. In this regard,  we can enhance > week to reflect number of days left. 

History and access control will make it really good for corporates.  I use separate installations.



jel...@gmail.com

unread,
Mar 11, 2015, 3:12:43 PM3/11/15
to kanb...@googlegroups.com, jel...@gmail.com, vhvhvh...@gmail.com
Hi,

thank you, this are valuable remarks! Some notes, questions inline

Tomas


On Wednesday, March 11, 2015 at 6:13:26 AM UTC+1, Venkatesh Hegde wrote:

Currently i have been using Initials: task

it is very helpful to visually see who is assigned to what.

What about something like this: I could define some variables like ${userName} ${dueDateNumOfDayes} ${dueDateNice} ${shortDescription} ${longDescription} ${taskId} etc. 
Than in the board dialog provide a way to configure a template for all tasks in the board, separately for header and body. In your case it would look like this:
for header this: ${taskId} ${dueDataNumOfDayes}
for body this: ${userName}: ${shortDescription}

and than for each task it would be replaced by the actual values. What do you say?

 

I believe this tool has potential to be one of the best. Great job !


Thank you :)
 

I have been trying to triangulate workflow,  task and project management.

Workflow view helps in knowing that tasks have been planned and using color coding one can indicate that tasks are stuck.

BTW now Im working on the tagging feature - so you will be able to set a tag "blocked" on a task. It will be filterable according to it. It is basically partially implemented just not really polished yet. But Im already using it in my setup...
 

From an individual perspective,  tasks make more sense.  Filter feature does that for you.

Now when it comes to dates,  this tool is lacking to mark tasks as done.

why not just move them to the "done" workflowitem? I'm missing something here... But maybe the tags will help you with this once released.
 

Or to put in estimates as number of days

For estimates you could use the "due date" field. Maybe could be enriched by "num of days from now"? Would that make the trick?
 

,  or export as csv file.

for this the API can be used (https://code.google.com/p/kanbanik/wiki/API) - it is not too nice - you can see the heritage of the GWT RPC from which it has been refactored to this. But it is complete - frontend talks to backend only using this api so everything what can be done is done using this api. 

I have implemented some while ago for this bug (https://code.google.com/p/kanbanik/issues/detail?id=48) a simple python script which takes all the tasks and exports them as JSON. You could maybe enrich it to convert the output to CSV? 
It should be fairly simple. Do you think you could do it? You can find it as an attachment for the mentioned task (katufi.py).
 

In this regard,  we can enhance > week to reflect number of days left.

yeah, using that variable. The "> week" was meant as a feature, some things just don't always work out :)
 

 

History and access control will make it really good for corporates.  I use separate installations.

yeah, I know Im lacking here. For statistics it should be enough to implement some incremental export to excel or something and having the graphs etc there. And the access control is on roadmap, but Im not yet there...

How many installations if I may ask? And how many users? And how long are you using Kanbanik? Just out of curiosity ;)
Reply all
Reply to author
Forward
0 new messages