UI > Tasks > taskEdit > Feature (done?)

task categories / #1726

Summary

v0.08
done?
Aug 31, 2006
4 hours ... 2 days
100%
Dec 26, 2006
Aug 31, 2006 / pixtur
Dec 27, 2006 / pixtur
pixtur
 

Attached files

Summary
taskEdit_shaded.png
taskEdit_shaded.png

40709 bytes / ID 1727 / Sep 1, 2006
Show Details
 
After doing some further usability tests and having some more streber users to get feedback from, I decided to first refine the handling of tasks before adding any more features. Currently the task list gets very obscure when having too many tasks.

Problems:
  1. Wiki pages start to mix up with todo-tasks and bugs (once there are too many, you no longer find the stuff to do)
  2. Wiki pages require a different render style (we do not need assignment stuff here).
  3. Most users do not "dare" to create tasks for wiki-pages.
The solution is a very firm distinction between task types:
  • Tasks / Bugs
  • Folders
  • (wiki) pages
  • Events (comming up)
  • Milestones
  • Versions
Changing the type (between Task, Folder, Page, Event) becomes a separate function. You cannot turn a task into a Milestone or Version.

Benefits:
  • Much clearer interface:
    • easy to read todo list
    • well structured edit dialog
    • we do not need a quick edit dialog for Wiki-Pages
Tradeoff:
  • This intermixes with Labels (some user might already have used them to structure like this, but we cannot use labels to detect Pages because they are user-defined).

5 Comments

madlyr

Oct 27, 2006
version 3
Tom, could you explain a little bit more about tradeoffs?
Does it mean that current labels will be changed to Task, Bug, Folder, Event, Page, Milestone, Version?

pixtur

Oct 30, 2006
Labels will not be touched...
This will be an additional field which is may initialized by the names of assigned labels. But when I then change the category of a taks to "documentation" assigning it the label "Bug" might be confusing...
I thinking about adjusting the default values for "new" projects...


pixtur

Nov 7, 2006
started implementation...
As stated in Project Documentation I added two categories Task and Documentation. In noticed that refactoring the current usage of is_folder and is_milestone is really tricky. Actually this should be refactored into Categories but this is really tricky...


madlyr

Dec 5, 2006
version 2
Fixed disappeared folders and tasks in rev. 214
It was bug in implementation from rev. 201.

When adding new task to existing one (not folder) as subtask, then after that update folder and that subtask disappeared.

Effect: to see that folder and subtask, you have to view disappeared folder parent, etc. - weird behaviour.

-> Tom I think list vie should rely only on category filed, not partially on is_folder.

Reason: after task update is_folder was 0 and category = TCATEGORY_FOLDER. It should be is_folder = 1.

pixtur

Dec 11, 2006
version 2
 

Comment / Update