Revision as of 09:23, 7 October 2014 by Mbensi (talk | contribs) (→Complete base workflow)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 Context 2 User Stories 2.1 Inbox and base editing 2.2 Projects and task hierarchy basics 2.3 Complete base workflow 2.4 Base workflow convenience 2.5 Context basics 2.6 Context conveniences / Complete projects 1 2.7 Complete contexts 1 / Complete projects 2 2.8 Complete contexts 2 2.9 Notes and topics basics 2.10 Complete notes/topics / Task advanced edition bases 2.11 Notes convenience 2.12 Workday view basics 2.13 Workday view convenience 2.14 Complete topics / Purge 2.15 Task advanced edition + Delegation 2.16 Munich 2.16.1 Delegation 2.16.2 Folder selection (same for notes and todos) 2.16.3 Tags/Contexts 2.16.4 Sorting 3 Mockups 3.1 Mockups by Björn Balazs 3.2 Mockups by Christian Mollekopf Context Context is a meta-data concept. Since todos/tasks can be related, for instance, to a specific project, it would be nice to express this semantic link : that's where Context rises up. You, as a user, will be able to link any kind of context name to a todo helping you to organize and give the semantic you want them to have. Akonadi Backend : The context concept is stored into akonadi through the Akonadi Item Tag. An item holds a list of Tag that have a name and can be from diffents type. As a convention, a tag related to the type "context" would be zanshin related, its name, that will be displayed to the user, will depend on what the user as set. User Stories Requirements for Zanshin in the User-Story format, sorted by priority. Inbox and base editing display the inbox in order to see the notes and task which need to be orginazed (e.g. any task or note not associated to any project, context or topic) create task by typing a title in the Inbox in order to collect ideas while reflecting on my life mark a task as completed in order to have a warm feeling about getting it done delete a simple task so it is removed in order to clean old useless tasks modify the due date in order to know when the task has to be completed Projects and task hierarchy basics Select project to see the notes and tasks it contains Create project Associate a task to a project (associated to only one project) Associate a task to a task ( only one parent task ) Complete base workflow Dissociate a task from a project (get back in inbox) deleting parent task with all its children set in order to clean old useless tasks, in such case the user will be warned Filter out tasks which do not match by title nor text in order to find specific tasks can visually distinguish critical tasks that have past the due date with a different aspect in order to have them stand out Base workflow convenience create a task from Krunner by typing a title in order not to forget the current idea I'm having. create task by typing its title in a project area in order to refine my project steps modify a title of a task in order to fix a typo or refine its definition can see tasks that need to be done for today with a different aspects in order to have them stand out Context basics select a context in order to see all its associated tasks Create a context Display the Context view in order to see all existing contexts Associate a task to a context in order to describe the task resources (can be a person) Context conveniences / Complete projects 1 create task by typing its title from the context view in order to add faster a task associated to a context keep task without natural project ( recurrent task for instance) Delete project ( delete all its content ) Complete contexts 1 / Complete projects 2 Delete a context (if a task isn't associated with any context or project, it is not deleted but sent to the inbox) Associate a context to a parent context ( Warning : topic can have only one parent context ) Rename a project Dissociate a task from a context in order to fix a mistake Dissociate a task from a project (associated to only one project) Rename a context Complete contexts 2 Dissociate a context from a context Notes and topics basics Display the Topic view in order to see all exisiting topics Associate an existing note to a project (associated to only one project) Associate a note to a topic in order to organize knowledge Select a topic in order to see all its associated notes create note by typing a title from the Inbox in order to collect knowledge Create a topic Complete notes/topics / Task advanced edition bases modify the text of the task in order to save details about a task or add additional information Rename a topic modify a text of the note in order to save details about a note or add additional information Delete a topic (if a note isn't associated with any topic or project, it is not deleted but sent to the inbox) Notes convenience create note by typing its title in a project area in order to collect project specific knowledge create note by typing its title in a topic area in order to organize personal knowledge around this topic Dissociate a note from a topic in order to fix a mistake modify a title of a note in order to fix a typo or refine its definition Workday view basics display a workday view (start date or due date in the past) in order to know what I'm supposed to do modify the start date of tasks for today in order to have them plan from today (today view for instance) Workday view convenience modify the start date of a task in order to schedule it for a given day Filter out task with a start in the future in order to focus on what I should work on now filter out completed task views in order to focus on what is remaining only Complete topics / Purge Associate a topic to a topic ( Warning : topic can have only one parent topic) Dissociate a topic from a topic in order to fix a mistake purge all completed task in order to clean my tasks lists Task advanced edition + Delegation modify the progress information of a task in percent in order to roughly know how much work is left modify the duration information of a task in order to give a estimation on this workload Can propose to someone a task delegation in order to offload work to someone else task get associated to a context corresponding to a person notification got sent to the person Technical story : Given a delegated task, when it gets modified the notification is sent to the relevant user Munich Delegation As a user I want to delegate a task to another user. As a user I want to monitor progress of a delegated task. As a user I want to accept or decline a task that was assigned not me. Folder selection (same for notes and todos) As a user I want to see tasks in a selected folder As a user I want to see tasks from multiple selected folders As a user I want to maintain a list of visible although not necessarily selected folders, so I can quickly enabled the folders as required. As a user I want to search for new folders to enable, that will then appear in my folder list. As a user I want to remove folders from my currently visible list. As a user I want to create new folders As a user I want share my folders with other users As a user I want to see to whom a shared folder belongs. Tags/Contexts While contexts are tags too, we also need plain tag support. This is to have a uniform tagging mechanism accross email and calendaring objects. I'm going to refere to a tag of type "context" with context and to a tag of type "PLAIN" with tag. For tags I think filtering only is sufficient. Note that plain tags have no hierarchy. As a user I want to filter tasks and notes by tag/context. As a user I want to assign tags/contexts to todos/notes. As a user I want to create new tags/contexts. Sorting As a user I want to sort by title, end-date, due-date, priority, degree of completion Mockups Draft UI Mockups, not final. Mockups by Björn Balazs File:20120212 ZenshinMockup.ep.zip Mockups by Christian Mollekopf File:Cmollekopf zanshinmockup 30 5 2014.ep.zip Retrieved from "https://community.kde.org/index.php?title=Zanshin&oldid=39797" Content is available under Creative Commons License SA 4.0 unless otherwise noted.