|
2098 | User Interface | Bug Report | Medium | Attached image cannot be downloaded | Closed | |
| 1.1 devel | | 30.01.2016 | 17.02.2020 |
Task Description
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.
|
|
2056 | Backend/Core | Feature Request | Low | Do not do pagination on csv export | Closed | |
| 1.1 devel | | 17.09.2015 | 05.10.2015 |
Task Description
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.
|
|
2011 | Backend/Core | Feature Request | Low | last modified table sorting | Closed | |
| 1.1 devel | | 18.07.2015 | 20.07.2018 |
Task Description
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.
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
|
|
1979 | User Interface | TODO | High | Update bugs.flyspray.org | Closed | |
| 1.1 devel | | 18.03.2015 | 11.07.2016 |
Task Description
This site itself should be updated immediately to the current alpha version. We should eat our own dogfood.
|
|
1942 | User Interface | Feature Request | Low | Able To add a comment while editing a task | Closed | |
| 1.1 devel | | 13.11.2014 | 24.11.2015 |
Task Description
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
|
|
1835 | Backend/Core | Bug Report | High | Upgrade to 1.0 requires dokuwiki syntax vs. free text/h ... | Closed | |
| 1.1 devel | | 26.02.2013 | 19.09.2015 |
Task Description
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.
|
|
1776 | User Interface | Bug Report | Low | Arrow showing the last visited task broken when using ' ... | Closed | |
| 1.1 devel | | 16.10.2012 | 04.09.2015 |
Task Description
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.
|
|
1584 | Backend/Core | Feature Request | Low | Configuration: Header of emails | Closed | |
| 1.1 devel | | 07.07.2009 | 09.03.2015 |
Task Description
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"
|
|
937 | User Interface | TODO | Low | New fancy layout for 1.0 | Closed | |
| 1.1 devel | 2 | 29.05.2006 | 19.07.2018 |
Task Description
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.
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:
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.
|
|
1982 | Backend/Core | Bug Report | Low | double entries in assignees list | New | |
| 1.1 devel | | 20.03.2015 | 11.02.2016 |
Task Description
maybe yet fixed in 1.0 dev, but here bugs.flyspray.org my account is shown twice for selection if u edit a task.
Internally in the form also with the same id, so probably not a big problem.
I registered some years ago, maybe this year jordan(?) added me again or with another email adress? Maybe I have two addresses under on account here, which is a feature, not a bug.
But for the assignee list it should “group by user_id”.
|
|
1973 | Backend/Core | TODO | Low | url rewrite | Planned | |
| 1.1 devel | | 14.03.2015 | 11.02.2016 |
Task Description
Well, it needs a cleanup, per example:
fixed now http://127.0.0.1/flyspray/task/3?project=1
That should be something like:
The actual one is actually half a rewrite and half a GET version
|
|
1966 | User Interface | Feature Request | Low | My votes on myprofile | New | |
| 1.1 devel | | 11.03.2015 | 03.11.2015 |
Task Description
We keep the votes, because a task can be reopened everytime and then the old voters and votes should be visible again. In this case the amount of votes on active task could be a bit greater than allowed, but thats no real problem. The calculation of done votes and available votes based only on open task and project voting limit.
For example on uservoice.com you have 10 voting points. So you as user has to decide where your priorities are to put your votes.
So all users have more or less the same power to vote for tasks.
|
|
1836 | Backend/Core | Feature Request | Low | Need permission option to view only own tasks | Planned | |
| 1.1 devel | | 27.02.2013 | 22.04.2015 |
Task Description
In global permissions there is 'View tasks'. This makes it so a user can view all tasks. Need a way instead that they can view only their own tasks, for example a permission called 'View own tasks'.
If 'View own tasks' is checked for a user, in the project list we should only show projects which contain tickets that that user is a part of. Within a given project we should then only show tickets that the user is a part of if they have that permission set.
So for example if 'View tasks' is set, show user all tasks. 'View tasks' is not set, but 'View own tasks' is set then show them only their own tasks and projects.
|
|
1919 | Backend/Core | Bug Report | Low | AJAX Quick-Edit on category and task pages | Planned | |
| 1.1 devel | 1 | 09.07.2014 | 07.12.2015 |
Task Description
Ability to click field to edit ticket
TODO: return handler if request ok or fail.
TODO: also clicks on label should trigger show form.
Maybe the whole “click to active for editing this field” to one click too much. So if the user has the rights to edit the value the form input or action button should be shown when viewing a task. All other people just see the value if they have the right to view the value.
|
|
2012 | Backend/Core | Feature Request | Medium | Managing Tags | New | |
| 1.1 devel | | 18.07.2015 | 12.11.2015 |
Task Description
Tags can only be added on the "new task" page, not managed on the "edit task"-page.
|
|
1969 | User Interface | Feature Request | Low | search form with Advanced search toggle layout | New | |
| 1.1 devel | | 12.03.2015 | 19.09.2015 |
Task Description
I think the button advanced search button should not be placed right beside seach input field as full button.
Maybe a small down arrow under the simple search form with a horizontal line and a title tag as tooltip.
Any comments?
|
|
2031 | User Interface | TODO | Low | Rendering overdue | Planned | |
| 1.1 devel | | 12.08.2015 | 14.08.2015 |
Task Description
One of my task has 8.9166666666667 days left. This is very very very very accurate !
A rounding would look better !
Running Alpha2 now, Cannot use this on 'reported version' here on this site
Edit: Rounding is adhoc fixed on 2015-06-21 in dev in template file, but code should IMHO be centralized, not template, see comments
|
|
2018 | User Interface | Bug Report | Low | review keyboard navigation | Researching | |
| 1.1 devel | | 26.07.2015 | 29.07.2019 |
Task Description
Keyboard navigation is not documented
At least there is no hint in the interface which keyboard shortcuts are available for fast navigation between task list and task details view.
Due to the dropping of the cookie storage for remembering last search or last selected task in favor of not interfering when multiple flyspray browser tabs are open (with e.g. different projects) , the caret list browsing with ‘j’,’k’,’o’ and details view isn’t useful at moment.
keyboard based navigation must be documented somewhere, e.g. by providing hints (clickable icon for info or :hover ) at appropriate positions.
navigation flow and technical realisation reviewed for keyboard power users
Edit: Currently handled by js event handler:
j move cursor down in task list
k move cursor up in task list
o open current selected task in task list
n next task on task details page
p previous task on task details page
grep -r 'accesskey' *
Current accesskeys (browserspecific + key):
a double usage for new task and newmultitask. Must hit [Enter] to open one of them; on newmultitask page it adds a new row.
e edit task on task details page
f copy firstline to the other rows on new multitask page
l show loginbox or logs you off
m toggle mysearchesbox
r reset? when dokuwiki plugin is used
s submit when dokuwiki plugin is used
w watch/unwatch task on task details page
n next task
p previous task
y close task
|
|
1975 | Backend/Core | Feature Request | Low | Batch processing of tasks in tasklist | Planned | |
| 1.1 devel | 1 | 15.03.2015 | 13.12.2016 |
Task Description
E.g. actual version, dueVersion, ...
Edit by peterdd: Topic was discussed earlier on https://github.com/Flyspray/flyspray/issues/130 (edit:It seems Jordan turned “issues” on github.com off in favor of bugs.flyspray.org)
The feature still exists but it is turned off until finished in a secure way. The possibility of sub and parent tasks requires many checks.
|
|
1849 | Backend/Core | Feature Request | High | Installer Overhaul | Planned | |
| 1.1 devel | | 15.03.2013 | 15.07.2016 |
Task Description
The application installer needs an overhaul, all strict notices fixed and the associated dependant tasks resolved.
|
|
1736 | User Interface | Feature Request | Low | Be able to add colors for Task Statuses | Planned | |
| 1.1 devel | | 16.05.2012 | 15.10.2015 |
Task Description
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.
|
|
1671 | Database Queries | Feature Request | Low | Ability to extract CSV, or Excel | Planned | |
| 1.1 devel | 3 | 18.12.2010 | 08.10.2017 |
Task Description
At work, we would need to be able to do extractions from the list of regular Flyspray tasks. Have you the ability to integrate this functionality into the interface later.
|
|
1510 | Notifications | Feature Request | Medium | Function to test mail configuration | Planned | |
| 1.1 devel | 3 | 29.10.2008 | 28.10.2015 |
Task Description
Add a button to test mail configuration before notifications is accpeted
|
|
1487 | Authentication | Feature Request | Low | LDAP(Active Directory) Authentication | Planned | |
| 1.1 devel | 11 | 21.05.2008 | 04.09.2019 |
Task Description
I have done a very quick bit of work to bring ldap (through active directory) authentication to flyspray for our implementation in the office. I hope it will be of use to others. There is a readme.txt inside talking through the process and the patch to apply. My plan is to expand on this and make it part of the setup process but this will take a bit longer.
|
|
2000 | User Interface | Feature Request | Low | Responsible persons column view | New | |
| 1.1 devel | | 22.06.2015 | 09.09.2015 |
Task Description
In the task list the responsible persons are shown as "first person name, +n" where n are the count of further responsible persons.
I think this can be done a bit better.
Ideas:
show as it is now, but on css :hover show all persons
use initials like "CR FS JM" for Cristian R., Florian S., Jordan M. and on css :hover show a list with the full names, this can make the column width a bit smaller.
-
|
|
1861 | Backend/Core | Bug Report | Medium | Login-Page should redirect after login to the page, the... | Confirmed | |
| 1.1 devel | 1 | 12.04.2013 | 09.07.2018 | |
|
1040 | User Interface | Feature Request | Low | Close Multiple Tasks at once | New | |
| 1.1 devel | 3 | 17.08.2006 | 01.10.2015 | |
|
2317 | User Interface | Bug Report | Medium | Date format wrong | Confirmed | |
| 1.1 devel | | 22.11.2016 | 22.11.2016 | |
|
2118 | User Interface | Feature Request | Low | Show overview of existing tags for users | Assigned | |
peterdd | 1.1 devel | | 09.04.2016 | 26.10.2019 | |
|
1970 | User Interface | Feature Request | Low | Icons for predefined task types | New | |
| 1.1 devel | | 12.03.2015 | 30.10.2015 | |
|
1967 | User Interface | Bug Report | Low | Keep browser scroll position when sorting task list | New | |
| 1.1 devel | | 12.03.2015 | 19.09.2015 | |
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 | |
|
1847 | User Interface | Feature Request | Low | Make default theme responsive | Planned | |
| 1.1 devel | | 14.03.2013 | 16.10.2015 | |
|
1812 | Backend/Core | Feature Request | Low | Multiple email addresses | Planned | |
| 1.1 devel | | 17.01.2013 | 30.12.2015 | |
|
1751 | Backend/Core | Feature Request | Medium | Default to show all in Event Log | Confirmed | |
| 1.1 devel | 1 | 20.06.2012 | 09.02.2016 | |
|
1673 | Backend/Core | Bug Report | High | Only white screen after upgrade to 1.0 - reasons | Confirmed | |
| 1.1 devel | 4 | 12.01.2011 | 17.08.2016 | |
|
2139 | User Interface | Feature Request | Very Low | Add project setting of popular used programming languag... | New | |
| 1.1 devel | | 17.06.2016 | 17.06.2016 | |
|
2126 | User Interface | Feature Request | Low | dynamic meta description (was: Change page title) | Confirmed | |
| 1.1 devel | | 17.05.2016 | 17.05.2016 | |
|
2055 | Backend/Core | Bug Report | Low | Make the csv export table fields respect the user permi... | New | |
| 1.1 devel | | 17.09.2015 | 17.09.2015 | |
|
2053 | Backend/Core | Bug Report | Low | ambiguous user name display username / realname | New | |
| 1.1 devel | | 17.09.2015 | 19.02.2020 | |
|
2022 | Backend/Core | Feature Request | Low | default or auto options for some settings | New | |
| 1.1 devel | | 03.08.2015 | 15.01.2019 | |
|
2020 | XMPP/Jabber | Feature Request | Medium | Function to test jabber/xmpp configuration | New | |
| 1.1 devel | 1 | 31.07.2015 | 19.09.2015 | |
|
2019 | User Interface | Feature Request | Medium | title -tag | Waiting on Customer | |
| 1.1 devel | | 26.07.2015 | 26.07.2015 | |
|
2016 | User Interface | TODO | Medium | heading and h1, h2, h3 | New | |
| 1.1 devel | | 23.07.2015 | 23.07.2015 | |
|
2005 | Backend/Core | Feature Request | Low | one account, several authentications | New | |
| 1.1 devel | | 18.07.2015 | 18.07.2015 | |
|
2004 | User Interface | Bug Report | Low | php notice on unset params on reports page | New | |
| 1.1 devel | | 18.07.2015 | 19.09.2015 | |
|
1990 | User Interface | Feature Request | Low | Roadmap view should also show due dates and sort each v... | Confirmed | |
| 1.1 devel | | 17.04.2015 | 24.04.2015 | |
|
1981 | Backend/Core | TODO | Low | Unify event logging and notifications | Confirmed | |
| 1.1 devel | | 20.03.2015 | 22.03.2015 | |
|
1976 | Backend/Core | Feature Request | Low | Save sorting for actual project | Planned | |
| 1.1 devel | | 15.03.2015 | 15.03.2015 | |
|
1972 | User Interface | Feature Request | Low | Advanced search form - ideas for faster/better usabilit... | New | |
| 1.1 devel | | 12.03.2015 | 18.03.2019 | |