← Zanshin You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. = 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 == * <strike>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)</strike> * <strike>create task by typing a title in the Inbox in order to collect ideas while reflecting on my life</strike> * <strike>mark a task as completed in order to have a warm feeling about getting it done</strike> * <strike>delete a simple task so it is removed in order to clean old useless tasks</strike> * <strike>modify the due date in order to know when the task has to be completed</strike> == Projects and task hierarchy basics == * Associate a task to a project (associated to only one project) * Select project to see the notes and tasks it contains * Create project * Associate a task to a task ( only one parent task ) == Complete base workflow == * Dissociate a task to a task * 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 * <strike>can visually distinguish critical tasks that have past the due date with a different aspect in order to have them stand out</strike> == 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 * <strike>modify a title of a task in order to fix a typo or refine its definition</strike> * <strike>can see tasks that need to be done for today with a different aspects in order to have them stand out</strike> == 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 == * Associate an existing note to a project (associated to only one project) * 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 = Mockups = Draft UI Mockups, not final. == Mockups by Björn Balazs == [[File:ZanshinMockupBjörn.png]] [[File:20120212_ZenshinMockup.ep.zip]] == Mockups by Christian Mollekopf == [[File:ZanshinMockupProjectViewCMollekopf.png ]] [[File:Cmollekopf_zanshinmockup_30_5_2014.ep.zip]] Return to Zanshin. Retrieved from "https://community.kde.org/Zanshin"