Flyspray - The bug killer!

This is the Bug Tracking System for the Flyspray project. This is not a demo!

2019-04-22: Flyspray 1.0-rc9 released See https://github.com/Flyspray/flyspray/releases

IDCategoryTask TypeSeveritySummaryStatusProgressAssigned ToDue In VersionOpenedLast Edited
 1174 Backend/CoreTODOMedium TODO List for 1.0 Closed
100%
1.0341927.01.200702.03.2016 Task Description

A list what could/should be done for 1.0

  • language for email/jabber notification currently depends on sender(user who changes something), not the recipients preferences - needs loading translation everytime to the recipients prefered language changes in the sending loop. done.
  • Provide functionality similar to bugzilla 3.0 “whining” (Custom scheduled notifications) reminder (schedule.php) is working again . Setup a cronjob for that.
  • get rid of modify.inc.php (make do-modes pluggable)
  • database transactions
  • new templating engine (eval free)
  • user area (summed up notifications, own notes)
  • remove the usage of $_REQUEST and the Req class (only reduce)
  • add two checkboxes SSL and TLS to the SMTP configuration section in order to permit usage on servers that requires them (f.e gmail)
  • permit multiple flyspray installations with a single codebase.
  • Make threaded mail really work.
  • Localize the Installer/Upgrader
  • Upgrade to SwiftMailer v3 (when released for PHP4)
  • simplify task changes ( FS#1203 )? quick-edit is enough
  • link to dokuwiki syntax
  • replace FS prefix
  • lock password capability?
  • auto-close tasks...
  • restrict assignees (group permission → “show for assignees”, default 1)
  • last-edited-by column, others,  FS#1330  (redundancy table?)
  • for upgrading, to not make all fields project level?
  • remove all usage of split() and ereg_* functions, this include sending patches to external libraries.
  • Social networking authentification (Google, OpenID, Oauth, Facebook, Yahoo)

Things that will not be done in 1.0:

  • conversion scripts for most popular BTS - All of Flyspray data is stored in database. It should not be too hard to create a conversion script, at least from the Flyspray side. Do you need a conversion script to or from Flyspray? Tell us.
  • allow personal ordering of fields (FS 1.1 or later), see FS#2013
  • Add an option for SSL login - If you want a secure Flyspray, configure your webserver to only talk TLS/SSL, not unencrypted HTTP. Flyspray can help by hardening its source for TLS/SSL only sending, ask peterdd if it’s a requirement for you.

Things planned for 1.1:

  • Find no longer used functions in the code and remove them

Not planned yet:

  • Add support for both sqlite and mssql. But you can try your own experiments, we use adodb that supports a wide range of databases.
Showing tasks 51 - 51 of 51 Page 2 of 2 - 1 - 2

Available keyboard shortcuts

Tasklist

Task Details

Task Editing