• [admintrivia] sync the assembla implementation with [latest on github master -> https://github.com/canneverbe/flyspray]]

• native effort tracking

• native effort tracking

Should

• "native" effort tracking

• visual diff for Subversion commit - link to rev#123 shows list of affected files + their diffs (like Assembla or Redmine does)
• Flyspray -> wiki integration (have [[WikiSpace/PageName]] syntax link to given page off a per-project base URL)

• "native" effort tracking

• automatic summing for "all in current task list"
• in Roadmap, show "thermometer" for effort spent on closed tasks vs total effort planned for the given Version
• NTH: summing for "depends on"
• NTH: for Due in Versoin, percentage + count of tasks that have no effort estimate
• burndown chart for Due in version

• fields: original estimate (write once), current estimate (overwrite-able), time spent -- all in hours, all edits logged in task history

• NTH: for all team members: table "how many hrs / week I can allocate for this project" => total weekly time budget, needed for burndown

• burndown chart as part of Roadmap page: Version has start and delivery date, "Due in version" groups tasks for its milestone/iteration, NTH: team's weekly budget gives total time available for the version, task estimates eat from this budget => burndown

• API
• Subversion -> Flyspray integration (API or simple one-purpose .php script call on commit hook, close FS#123 and similar syntax in svn commit message adds a comment to the given task with the commit message plus link to changeset; even better would be to enforce task changes)
  • syntax see http://code.assembla.com/cosi/subversion/repo/instructions
  • Assembla webhook suffices for now, repo scripts can be added anytime later

• the task detail page should have input field on "This task blocks these from closing" to add dependencies directly, same way as "Depends on"

• visual diff for Subversion commit - link to rev#123 shows list of affected files + their diffs (like Assembla or Redmine does)

Done

• improve mass edit task data (from tasklist / search results page)
  • in "all projects" task list, only global fields are editable
  • in single project list, all task fields are editable
• custom fields (like Assembla, including treating most of the predefined as custom ie ability to disable)
  • they are implemented in 1.0.0.dev on flyspray.org, let's check that first
  • what should we have: add own field(s) including basic type (number/text/...), add custom field to task list, search/filter uses custom fields; nice to haves: disable std field(s)
• check on Assembla, other SVN repositories Flyspray -> subversion (+ mercurial, git) integration (have rev#123 turned into hyperlink to ViewVC page of the given changeset, per project)
  • better: project config = URL of svn/... web access with placeholders for project name and revision number

• fields: original estimate (write once), current estimate (overwrite-able), time spent -- all in hours
• add "number" as custom field type
• for all team members: table "how many hrs / week I can allocate for this project" => total weekly time budget, needed for burndown

• burndown chart: Version has start and delivery date, "Due in version" groups tasks for its milestone/iteration, team's weekly budget gives total time available for the version, task estimates eat from this budget => burndown

• usability of task list
  • default sort order for task list, per project / user
  • strikethrough closed issues

• issue and comment submission via email

• the task detail page should have input field on "This task blocks these from closing" to add dependencies directly, same way as "Depends on"

• Assembla webhook suffices for now, repo scripts can be added anytime later

• "copy issue id and summary to clipboard" => use via "paste" eg in svn -m log message

Some notes by the developer: http://www.evernote.com/pub/jendarybak/flyspray

[3/3/2010] OK, some of the things are in 1.0.0.dev, reprioritized list is:

• improve mass edit task data (from tasklist / search results page)

• custom fields (like Assembla, including treating most of the predefined as custom ie ability to disable)

• check on Assembla, other SVN repositories Flyspray -> subversion (+ mercurial, git) integration (have rev#123 turned into hyperlink to ViewVC page of the given changeset, per project)

• API

• Flyspray -> wiki integration (have [[WikiSpace/PageName]] syntax link to given page off a per-project base URL)

• fields: original estimate, current estimate, time spent (all in hours), add "number" as custom field type

• what should we have: add own field(s) including basic type (number/text/...), add custom field to task list, search/filter uses custom fields; nice to haves: disable std field(s)

• they are implemented in 1.0.0.dev on flyspray.org, let's check that first

• Flyspray -> subversion (+ mercurial, git) integration (have rev#123 turned into hyperlink to ViewVC page of the given changeset, per project)
  • better: project config = URL of svn/... web access with placeholders for project name and revision number

• in "all projects" task list, only global fields are editable
• in single project list, all task fields are editable

• they may be implemented in the latest stable on flyspray.org, should check that first

• Mylyn connector

• Subversion -> Flyspray integration (API or simple one-purpose .php script call on commit hook, close FS#123 and similar syntax in svn commit message adds a comment to the given task with the commit message plus link to changeset; even better would be to enforce task changes)

• "native" effort tracking incl. ideally (=NTH) automatic summing for "all in current task list", "depends on" and "due in version" (+ burndown chart in this case)
  • fields: original estimate, current estimate, time spent (all in hours)

Nice to have (NTH)

• Subversion -> Flyspray integration (API call on commit hook, close FS#123 and similar syntax in svn commit message adds a comment to the given task with the commit message; even better would be to enforce task changes)

• syntax see http://code.assembla.com/cosi/subversion/repo/instructions

• Flyspray -> subversion (+ mercurial, git) integration (have rev#123 turned into hyperlink to repo or websvn page of the given changeset, per project)

• "native" effort tracking incl. automatic summing for "all in current task list", "depends on" and "due in version" (+ burndown chart in this case)

• usability of task edit (buttons on form top not bottom, screen positions of edit widgets as in view, if user has rights show task directly in edit mode?)
• hyperlinked values in task list and detail (version name -> all tasks due in that version, etc)

• "native" effort tracking incl. automatic summing for "depends on" and "due in version" (+ burndown chart in this case)

• hyperlinked values in task list (version name -> all tasks due in that version, etc)

• "native" effort tracking incl. automatic summing for "depends on", burndown chart

Must

Should

• "native" effort tracking, burndown chart

Nice to have

• default sort order for task list, per project / user
• simplified user interface + access rights to use for helpdesk / support / client issue reporting and tracking

• saved task list views - view defines columns, sort order

• default sort order for task list, per project / user

• simplified user interface + access rights to use for helpdesk / support / client issue reporting and tracking
• twitter etc integration (add Twitter as task change announcement channel)
• "copy issue id and summary to clipboard" => use via "paste" eg in svn -m log message

• Flyspray -> wiki integration (have [[WikiSpace/PageName]] syntax link to given page off a per-project base URL)

Flyspray, as easy and powerful as it is, sort of does not fly anymore - the development has been stalled for the last couple of years. So, here is a list of my favourite stuff to improve upon. Roughly decreasing importance:

• mass edit task data (from tasklist / search results page)
• custom fields (like Assembla, including treating most of the predefined as custom ie ability to disable)
• Flyspray -> subversion (+ mercurial, git) integration (have rev#123 turned into hyperlink to repo or websvn page, per project)
• API
• Subversion -> Flyspray integration (API call on commit hook, close FS#123 and similar syntax in svn comment to enforce task changes)
• effort tracking, burndown chart
• more/detailed/customizable statistics and reports (TBD needs elaboration)
• email issue and comment submission
• twitter etc integration (add Twitter as task change announcement channel)