|
2062 | User Interface | TODO | Low | review do=admin&area=editallusers | New | |
| | | 29.09.2015 | 15.04.2020 |
Task Description
Bugs
Small javascript issue: When checkbox of one users row clicked, it doesn’t select the checkbox because the row click event handler doubles the click (check and uncheck, tested with firefox41). Clicking in the row (not on the name) selects the checkbox. fixed
browser back button after delete of a user not working as expected. (fix it by redirect 303 , see modify.inc.php how it done for other form submits)
Missing features
no sorting possible of the table (like tasklist)
no pagination (like on tasklist) OK, probably not needed: ~2000 user registrations on bugs.flyspray.org and no problem rendering the table in browser. Archlinux has over 12k users and my test with 30k generated users showed problems handling the huge query results. So we need this!
no filtering of user list possible
no helpful information for admins like registration date and last time of login of users (last login time requires a new field in flyspray_users) implemented in Flyspray 1.0-rc7
no summary about users like how many exists or how many are currently online (requires storing sessions in a db session (e.g. flyspray_session) table instead php default session directory) on the install. Or a statistic graph of activity or peaks of new registrations over time.
maybe show user profile image too in the list.
choosable user field columns - partially implemented since 1.0-rc7 by selecting groups of user fields and calculated user fields: user stats, user settings
|
|
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
|
|
2654 | Backend/Core | TODO | Medium | PHP8.1 compatibility | New | |
| | | 19.10.2021 | 19.10.2021 |
Task Description
[ ] ADOdb xmlschema03 issues [ ] other warnings/notices
|
|
2620 | Backend/Core | TODO | Medium | PHP8 compatibility | New | |
peterdd | | | 26.11.2020 | 17.08.2021 |
Task Description
PHP 8.0 is now released (2020-11-26) and Flyspray should be made compatible with it.
The @ operator no longer silences fatal errors. Some checks in installer or other areas might not work anymore as expected when the @-operator was used as silencer for previous PHP versions.
|
|
2554 | User Interface | TODO | Low | keyboard shortcuts help box should adapt to current pag... | New | |
| | | 06.06.2019 | 06.06.2019 |
Task Description
The shortcuts help infobox should adapt to the current page type.
So when in editing a task for instance, the n (next task) and p (previous task) shortcuts are not available for a good reason. Listing them there with same priority as other keys then is not helpful.
The simpliest solution is probably putting some if-statements depending on the $do variable into CleanFS/templates/shortcuts.tpl ..
|
|
2143 | Translations | TODO | Very Low | jscalendar: week start should be monday, ISO 8601 | Confirmed | |
| | | 01.07.2016 | 03.03.2019 |
Task Description
The current jscalendar shows sunday as the first day of the week by default.
Could be modified for a language by adding
// First day of the week. 0 means Sunday, 1 means Monday
Calendar._FD = 1;
js/jscalendar/lang/calendar-XX.js
See also https://github.com/Flyspray/flyspray/commit/f7831b7f6845e237b79da2a68d475f21a24fff72#diff-70a18ca66e215fc5aa282d4c58fed4ab
It should default to Monday as defined by ISO 8601.
https://en.wikipedia.org/wiki/ISO_8601#Week_dates
https://en.wikipedia.org/wiki/Week#Week_numbering
|
|
1737 | Javascript | TODO | Low | Javascript Overhaul | New | |
| 1.1 devel | 1 | 25.05.2012 | 17.04.2021 |
Task Description
@scott wrote:
Convert all the JS to using one library. Seems there is scattered JS scripts all over and we need to pick one solution that could be long term and has plenty of features for improving FS.
I vote for JQuery w/ Bootstrap which has some nice JS effects using JQuery.
@peterdd wrote on 2021-04-02:
Yes, move inline javascript out of templates, but no need for single wholeinone js file, it’s ok to load only the js files required for current page. Probably in 2021 there is no need for js framework anymore and standard javascript is just fine for the functionality Flyspray requires.
|
|
2553 | User Interface | TODO | Low | intelligent accesskey shortcut helper dependent of OS, ... | New | |
| | | 06.06.2019 | 29.07.2019 |
Task Description
The HTML accesskey attribute feature is differently accessible dependent of operating system, web browser and web browser configuration, and users keyboard layout and user language.
By taking advantage of the User-Agent HTTP header value provided by default by web browsers, Flyspray could better know of what kind of keyboard and browser the user sits in front off and show the key combinations for the accesskey feature that best fits the users environment.
|
|
2016 | User Interface | TODO | Medium | heading and h1, h2, h3 | New | |
| 1.1 devel | | 23.07.2015 | 23.07.2015 |
Task Description
We should change the document logic a bit here. For public projects search engines like well structured pages more then others. And we get a consistent structure too in future for Flyspray.
This I have in mind
Project area name ("All Projects" or "Project name")
Admin setting / Project setting pages, title of the sub pages
Currently: h3-tag!
My wish: h1 tag
Section names in these pages
Task view page
Task name=summary
Currently: h2 tag
My wish: h1 tag
Task descriptions then can use structuring their task description starting as h2,h3,h4 (done by dokuwiki renderer for example)
Toplevel project overview /dashboard
Currently: h2 for each project name
My wish:
* keep h2 for each project name
* h1 for the page heading (maybe hidden by css)
New Task page
Reports page
Currently: h3 tag
My wish: h1 tag
Roadmap page
Currently: h3 tag for each milestone
My wish:
* h2 tag for each milestone,
* h1 tag for heading (maybe hidden by css)
MyProfile page
Currently: h3 tag for each section
My wish:
* h2 tag for each section
*h1 tag for heading (maybe hidden by css)
(Sure the theme.css must be adapted to this change.)
|
|
2587 | Backend/Core | TODO | Medium | display_errors=1 should not set in release candidate | Unconfirmed | |
| | | 18.12.2019 | 18.12.2019 |
Task Description
display_errors = 1 should not set in include/fix.inc.php for releases or releases candidate, because with this it is not possibele to disable the error reporting globaly.
The problem is, if I want to enable full error reporting to logfile via “error_log=…” in php.ini, then the error will also full reported to user. Full error reporting is a hig risk for security.
Did you installed an official release or did you used an inoffical docker?! flyspray-1.0-rc9
Steps done to create the problem: Create a file php.in in base directory with follow contens: error_reporting = E_ALL | E_STRICT log_errors = On display_errors = Off error_log = /var/log/php-flyspray-errors.log
Expected behavior: Errors only to log file
Experienced behavior: All errors goes also to user. The option “display_errors = Off” has no effect.
|
|
2008 | User Interface | TODO | Low | difference between related tasks and related links | New | |
| | | 18.07.2015 | 18.07.2015 |
Task Description
It should be made clear to the user what related links are in the "new task" and "edit task" form and what a user should input in these fields.
|
|
1956 | Backend/Core | TODO | Low | Dates | Confirmed | |
| 1.1 devel | | 07.03.2015 | 09.03.2015 |
Task Description
Upon my implementation for an easier date selector, I think we should rework it as follow:
|
|
2625 | User Interface | TODO | Low | avoid password manager popups in admin prefs area | New | |
peterdd | | | 10.02.2021 | 10.02.2021 |
Task Description
We must teach browsers not to use some input fields in the admin prefs area to offer to store it in their password manager.
Steps to reproduce:
Login with Firefox as admin into Flyspray. (Maybe other browsers behave same)
Go to admin prefs area (top right gear icon)
Click link somewhere else (so leaving admin prefs page)
Firefox browser pops up password manager as it detected some password input fields on admim prefs setting page. But in this case this is not wanted.
Either by using different input field names where the browser does not assume it is a login password field or find input field attribute to tell them.
auto-complete="off"
is not working anymore in browsers for password fields.
webbrowser: Firefox 85.0.2
Popup probably triggered by the password fields for configuring Email and XMPP notification: smtp_pass and jabber_password input fields. Firefox heuristic is too stupid to detect that these are for server configuration, not user login fields!
Neither
autocomplete="new-password"
nor
autocomplete="one-time-code"
attribute helped.
Stubborn Firefox ..
|
|
2573 | Backend/Core | TODO | Low | add rel nofollow,ugc,.. settings | New | |
peterdd | | | 14.09.2019 | 15.09.2019 |
Task Description
Find a good configuration name just reuse relnofollow as used by dokuwiki
Find a good translation keyword for that config relnofollow
Find a good translation keyword for config description (title attribute)
Goes into prefs table as it is sitewide configuration.
As first implementation a simple checkbox should be ok. Should be on the tab with other spam handling stuff like captcha configuration.
Is enabled by default (1). Adapt setup xml files, upgrade procedure.
|
|
2572 | User Interface | TODO | Low | add link attributes ugc and nofollow to user generated ... | New | |
| | | 13.09.2019 | 13.09.2019 |
Task Description
no task description |