• Status Planned
  • Percent Complete
  • Task Type Feature Request
  • Category User Interface
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version 1.1 devel
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by Viderizer - 16.05.2012
Last edited by peterdd - 15.10.2015

FS#1736 - Be able to add colors for Task Statuses

I often used color identifiers for my Task Statuses in my old bug tracking solution, and it helped me prioritize things, like confirming unconfirmed bugs. The only thing that currently has colors, is the severity- I’d like a possibility to have (customizable) colors for Task Statuses too.

scott commented on 17.05.2012 21:04

interesting idea. I also like to do this when i do excel sheets with google docs.


I like the idea. Would colors be tied to a priority and automatically set based on that, or would colors be set by the user on a task by task basis? Implementation of this one is easy, I think the harder part is figuring out all the details of the specification in terms of functionality and UI for all the minute details.


For example, would we color by severity? by priority? by user? by release? Only color manually if the user wants to – but then is a user realistically going to invest the time to color code every task? Are colors set by any user, or any by admins? Etc

Project Manager

Will be done by my work on systemwide and project setting pages, because the task field list management is similiar for most task properties.

Project Manager

The bad: Setting this in the admin and project settings will not be done in FS1.0.
Reason: Could not just be color, could also be a gradient, a border,icon, etc. so a lot of css config possible.

The good: You can do custom CSS. See themes/CleanFS/custom_example.css for inspiration.

(currently commented out in themes/CleanFS/templates/header.tpl until configuration can be made in the admin settings)

Flyspray caches CSS files (by .htaccess settings) for performance several days by the browser. So after a change of cssfile, press F5 to reload the files from server.

My best practice: After a change of a css-file store it under a different name, e.g. custom_20151015.css and adapt the settings to the new name, so also the web browsers of other people load the css as new file under any circumstances.

Here a screenshot of how the list look could be changed with some fontawesome fonticons rendered instead of text just with pure added css:


Available keyboard shortcuts


Task Details

Task Editing