Flyspray - The bug killer!

Steps:

- Attach an image to a task.
- It shows as a link in your task (cf. screenshot “Screenshot from 2016-01-29 18-34-31.png”).
- Click on the link.

Result: it opens a “popup” with the image displayed in it. If the image is big, the popup is just so huge the image is not visible without boring horizontal and vertical scrolling (see “Screenshot from 2016-01-30 15-07-26.png” which shows what I see when I click the image link on my task).
I can’t even right click to download from the menu since I see no “Save Image As” item. (see Screenshot-no-save-image-in-menu.png).

My workaround was that if I drag and drop the attachment link in the address bar, I finally get the expected image, which I can finally save as! This workaround was hard to find, and I expect most people will just get frustrated of being able to view an image attachment, yet not save it locally.

I proposes the following:
- a small “download” icon next to the image link in the task for direct download (without preview).
- a “download” link/icon on the top-left of the image display popup (to download while previewing).

And as a side feature (maybe I should make a separate report?), I suggest that by default the image display popup constrains the image to the screen size, with a “see real size” link, so that you don’t get the popup with huge scrolling when opening a big image on a smaller screen.

Note: of course this issue does not appear with non displayable attachment. If I have a zip or a document, it proposes me to download it directly.

The result of pressing the task list csv export button should not do pagination (limit on the database query)

The wanted download of the csv is in most cases a complete list of the task list search. So users can it simple import into OpenOffice Calc, LibreOffice Calc, MS Excel or for importing it somewhere else like another database.

Implementation of this task should be quite easy by just ignoring the limit and offset, because the same query is used for task list viewing and csv export.

If you sort the task result list by last modified date, it ignores the tasks, that are new created, but not changed.

I think better is to sort by create date too when sorting by modifed date.

• Either we do it by a modified sql sorting rule using both date fields.

• Or we just save the the creation date also in the modified field on the creation, so this field is never empty or null. (this would be the easiest)

In the 2nd solution the upgrade sql script should write the task creation datetime to the modifed datetime field
Something like

UPDATE tasks SET modified=created WHERE modified='' or modified IS NULL

This site itself should be updated immediately to the current alpha version. We should eat our own dogfood.

• modification in 0.9.9.7 on bugs.flyspray.org with password_hash() wasn’t ported to 1.0dev version, so some users of bugs.flyspray.org aren’t able to login now??? need to reset her password..? You just need to change passwdcrypt param from ‘md5’ (was default until FS1.0-rc1) to ‘crypt’.

There was a “nice to have feature” in the bluey them that allowed you to edit a task and add a comment at the same time that showed the changes, Can this be implememented into cleanFS if possible

comment field after editing:

Field changed: Status (Unconfirmed → New)
Field changed: Percent Complete (0% → 40%)
Test

As a result of adding CKEditor we now need to nicely handle previous installs data where dokuwiki syntax is still in situ.

To be completed in line with the upgrade process which also requires work.

Edit 2015-03-11 peterdd: Dokuwiki plugin will probably still be the default syntax plugin for FS 1.0. CKeditor with free HTML input adds too many security issues which weren’t not enough considered before. So we think Dokuwiki as the default is the better option for the release of 1.0.

Older installs of Flyspray use dokuwiki format.
Peoples who just used the later dev versions (after 0.9.9.7) of Flyspray used ckeditor/html as text format.

So the Flyspray userbase consists of 2 different content formats. We plan to provide automatic conversion options when doing upgrades of existing installations.

When you set 'address_rewriting' to '1' and activate the .htaccess, the arrow in front of the last visited task doesn't work.

I'm using FS 0.9.9.7.

Could be nice to add our own Header of the emails, for example, if my project is named FOO, i will receive emails like "FOO noreply@bts.foo.com", but if I own differents websites, could be nice to know from which one Im receiving the email from, so could be nice to set our own header (or it is just the name from?) of the emails, in order to receive something like "FOO Bugs noreply@bts.foo.com"

For version 1.0 we need a nice new layout for Flyspray.

Some ideas so far:

• The theme should be bright, clean, modern and colourful.
  • I personally think it should look a bit like http://www.oswd.org, “Web 2.0”
  • Also nice look and feel: http://fisheye1.cenqua.com/changelog/matheclipse/ (not a BTS)
  • A good attempt is Paul’s “Clean theme”, but it’s not very colourful/modern (dark grey parts are ugly) and there should be more significant layout changes. http://tasks.purecodes.org/?do=details&task_id=40
• Comments could be displayed like messages on Google groups (complies to the mentioned requirements), see attachments
• The menu needs to be changed. It probably has to be vertical in future, but in any case (the only point that matters) it should be possible to add more menu items without requiring a higher screen resolution (width)
• the new theme should use unstyled input elements
• the layout of all forms should be unified. I like the layout of phpbb for example (see attachment)

Layout bugs/problems that should be fixed:

•  FS#929 
•  FS#930 
•  FS#902 
• FS#1134
• more?

Currently we don’t have anyone who is able to do this (I would like to, but I am not very good at it), so if anyone is skilled at making things look good (without creating an image-heavy layout like some at css Zen Garden) he can let us know.

More ideas are welcome and will be added to the description.