Difference between revisions of "Worklist"
(Set PropertyValue: TargetDate = 2014-09-30) |
(Set PropertyValue: StartDate = 2014-06-01) |
||
| Line 37: | Line 37: | ||
Participants=Yolanda_Gil| | Participants=Yolanda_Gil| | ||
Progress=100| | Progress=100| | ||
| − | StartDate=2014- | + | StartDate=2014-06-01| |
Start date=28-April-2014| | Start date=28-April-2014| | ||
TargetDate=2014-09-30| | TargetDate=2014-09-30| | ||
Type=Low}} | Type=Low}} | ||
Revision as of 18:20, 25 July 2014
Contents
About this task
This task involves a design for a task worklist, and the implementation of this design.
STATUS: The design is completed. The implementation is not started yet.
The Design of Worklist
Accomplishing tasks works best with exactly one responsible person. Every task has a task leader which is defined within the structured properties. The goal of each task leader is to accomplish his tasks therefore he should know which tasks he leads. Searching with certain filters would work but it’s not very convenient. Above the expertise filter are two tabs, All Tasks and My Tasks. With the all tasks tab you can explore all wiki tasks.
Hierarchical View
The My Tasks tab shows all tasks hierarchical where the currently logged in user is the task leader. Behind the My Tasks label the number of currently open tasks is represented in red. The mockup shows exactly the same explorer like in the Explorer Navigation sample. The search and filter functionality works here as well.
List View
Viewing My Tasks in the hierarchical context based view may lead to a heavily nested structure. To ensure a simple representation the view can be switched to a flat list view. This view provides more detailed task information like the progress in percent within the pie and the left time below the task name. The list view allows sorting tasks by certain categories.
Comments and Feedback
Please comment everything might be interesting related to this task.
- ...
