r3 - 10 Jun 2007 - 02:35:50 - VeraSheinmanYou are here: OSAF >  Journal Web  >  TWikiUsers > VeraSheinman > VeraSheinmanNotes > DesignMeetingNotesMimiJeffrey

General vision

Mimi

  • vision of users' needs is summarized in: CollectionReportsBrainstorm
  • Users may have 3 basic needs:
    • get the feeling of the general states of affairs
    • see what is coming up during the next week
    • see everything in a compressed way so they can see all the things that were out of reach

Vera

  • additional need (may be postponed to a later stage) :
    • Discovering problematic management.
      • Discover items that keep being postponed.
      • Discover items that something about them got changed (e.g. priority)

Next week items

Mimi

  • It is perhaps the most important thing for users to know what is expecting them in the coming week.

Vera

  • It may be equally important to have an overview of the future unrestrained (incl. things for the next two weeks), based on the decisions made during the last week
    • For instance, if a new task of attending a conference in one month from now appeared in the last week, it may be important to see it in the report.

Later items

Vera

  • Items that were triaged as Later by users, may be important to see the transition of focus since the last week.
  • Generally, items that got some kind of new status (e.g. priority) may indicate transition of focus

Mimi and Jeffrey

  • Some items are triaged as Later automatically. Perhaps these should not be reported on.
  • Some items are kept being later because they are "Someday" items.

What collections should be included in the report?

Jeffrey

  • What is the default filter for the items in the report?
    • all the collections - strange, because there are not-mined collections
    • only the mined collections
    • only the selected collection - the simplest

Percentage of completion

Mimi

  • assuming swags for all items is contradictory with chandler's type of tasks. The tasks are usually more vague, and less well-defined than it is required for proper % of completion management. It is more suitable for heavier Project Management. Also, managing time-estimates requires the effort that chandler aims to spare from its users, allowing them creating very basic items and later transforming them to something bigger, if there is such a need.
  • % of completion may be useful for very well-defined tasks, as in an example of an interviewee that conducts tours weekly. She performs a set of 5 clearly defined tasks weekly. For her it would be easy to provide pretty accurate time-estimates
  • no subtasks in chandler yet - % of completion may be more appropriate for tasks that can be broken into subtasks. % of completed subtasks out of total may be then calculated.

All

  • % of completion is not something to begin with.

Dashboard view for reports

Vera

  • maybe it can remain the same (items aggregated by their triage status), but only the relevant items for the current report will be shown

Jeffrey

  • that is similar to search functionality, that is not yet working.

Misc

Mimi

  • reporting on items that remained unread since the last weekend
  • sharing may get complex: * reporting on changes of sharing
  • we have to decide what is the list of potentially useful items

Parcel or Chandler?

Vera

  • shall we design the project as an independent parcel or as a change within Chandler's code?

Jeffrey

  • In the current stage change in Chandler's code seems a better option.

The first step for progress reports project

Vera

  • In real-life reports are based on the previous reports. Shall we start with reporting based on an existing report, or just based on time?

Jeffrey

  • Provide a report for items from the last week:
    • /report is a command in the "Quick Entry" field. In the event of this command:
      • summarize the information textually inside the body of a note aggregating them by their triage status
      • refer only to the events from the currently selected collection

Vera's tasks for next week

  • Concise initial design proposal for design-list
  • In the local version of chandler:
    • make chandler understand /report command (by adding functionality to onQuickEntryEvent in parcels/osaf/views/main/Main.py)
    • extract the items from the selected Collection (getSidebarSelectedCollection()) and present textual summary in the body of an item of kind Note
      • #items that were created last week
      • list of their titles
      • #items with NOW status
      • list of their titles
      • #items with LATER status
      • list of their titles
      • #items that were marked as DONE during the last week
      • list of their titles
  • take note of all the process and the encountered problems on the way
  • compile and make sure that it works in chandler
  • report upon errors (svn diff)

-- VeraSheinman - 08 Jun 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.