|
2201 | API | Bug Report | High | I got Fatal Error on the Github OAuth | Unconfirmed | |
| 1.0 | | 07.09.2016 | 09.09.2016 |
Task Description
Fatal error: Class 'League\OAuth2\Client\Provider\Github' not found in /html/bugs/includes/GithubProvider.php on line 11
I have downloaded this: Precompiled with 3rd party libs for PHP5.6: flyspray-1.0-rc1_php56.tgz and the file seems really dont exist.
|
|
2112 | API | Bug Report | Medium | Assigned tickets aren't editable for lower privileged u... | Unconfirmed | |
| | | 31.03.2016 | 11.04.2016 |
Task Description
An assigned ticket can't be edited by a lower privileged user.
Steps to reproduce:
One Project, Two Users. User A is Admin, User B is Basic
A creates a Task.
A take ownership of the Task. (it’s important to do this AFTER saving the task. You cannot assign User A if you are A in this moment. Maybe another Bug...!?)
Now B is allowed to take ownershop too. B click now “Add me to assignees”.
Now B can edit the task.
If B click “save”, the task can’t be saved, because some fields haven’t the correct values (esp: state is now “unconfirmed”). Many error messages said, that unexpected values exist
Some weird moments:
Why can B edit a task? He have no rights to edit tasks...
If B are Basic and have “edit own Task”-Right too, this bug also exist.
|
|
1987 | API | Feature Request | Medium | REST API to get metrics from flyspray projects | Unconfirmed | |
| | | 29.03.2015 | 06.10.2015 |
Task Description
I need metrics for flyspray projects about a rest api. For example the count of issues for status, priority. I want use this values for my code analysis system http://www.sonarqube.org/ and other internal tools. It is possible to create a rest api with user authorization and only for metrics data?
|
|
2551 | Authentication | Information | Low | LDAP/AD integration | Unconfirmed | |
| | | 15.05.2019 | 04.09.2019 |
Task Description
Hi
Please advise if there are known issues when integrating Flyspray with Active Directory using LDAP.
|
|
2209 | Authentication | Feature Request | Medium | TLS support for LDAP | Unconfirmed | |
| | 1 | 09.10.2016 | 04.09.2019 |
Task Description
It would be helpful to have communication with LDAP via TLS
|
|
2107 | Authentication | Feature Request | Low | Support CAS Server Authenticate | Unconfirmed | |
| | | 02.03.2016 | 04.09.2019 |
Task Description
Please support Central Authentication Service, thank you.
|
|
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.
|
|
2629 | Backend/Core | Bug Report | Low | activating history tab sends same request 2 times | New | |
| | | 11.03.2021 | 11.03.2021 |
Task Description
There should be only one request to
js/callbacks/gethistory.php when activating the History tab
The request is made:
on mousedown event
on click event
So holding down the tab sends the first request and releasing sends the second request.
|
|
2627 | Backend/Core | Bug Report | Low | checkLogin: Trying to access array offset on value of t... | Unconfirmed | |
| | | 09.03.2021 | 11.03.2021 |
Task Description
FS version: 1.0-rc9 PHP version: 7.4.15 database: mysql php.ini: error_reporting = E_ALL | E_STRICT
Steps done to create the problem: - Login as Admin or User, with name “Admin”, not with email.
Experienced behavior: PHP Notice: Trying to access array offset on value of type bool in …/flyspray-1.0-rc9/includes/class.flyspray.php on line 812
A possible fix is attached as patch.
Think, it is this line in currend code: https://github.com/Flyspray/flyspray/blob/5b0a3d80fc9612ca8e8743450fbf2c8243b5bf47/includes/class.flyspray.php#L836
|
|
2626 | Backend/Core | Bug Report | Critical | Create a new build, last stable is 0.9.9.7 (2012-05-28)... | Unconfirmed | |
| | | 27.02.2021 | 11.03.2021 |
Task Description
The last build is very old, it is possible to create a new build? - The last RC: 2 years soon - The last stable: 9 years soon
GitHub Releases section: - https://github.com/Flyspray/flyspray/releases
Latest release
v1.0-rc9
136c339
Flyspray 1.0-rc9
@peterdd peterdd released this Apr 22, 2019
Stable: http://www.flyspray.org/docs/download/
Flyspray 0.9.9.7 - 28 May 2012
|
|
2621 | Backend/Core | Bug Report | Medium | php notice/warning when reopening in some circumstances | New | |
peterdd | 1.0-rc10 | | 27.11.2020 | 14.04.2021 |
Task Description
Reopening a task triggers a PHP notice with PHP7.4 under some circumstances. Reopening a task triggers a PHP warning with PHP8.0 under some circumstances.
Reproduce:
Create task
Close task directly without setting a completion percentage
Reopen the task
Notice: Trying to access array offset on value of type bool in /***/includes/modify.inc.php on line 684
Notice: Trying to access array offset on value of type bool in /***/includes/modify.inc.php on line 686
Notice: Trying to access array offset on value of type bool in /***/includes/modify.inc.php on line 686
|
|
2620 | Backend/Core | TODO | Medium | PHP8 compatibility | New | |
peterdd | | | 26.11.2020 | 11.03.2021 |
Task Description
PHP 8.0 is now released (2020-11-26) and Flyspray should be made compatible with it.
|
|
2617 | Backend/Core | Feature Request | Low | Preview button not at the good place | Maybe | |
| | | 26.09.2020 | 26.09.2020 |
Task Description
The “Preview” button is not at the good place.
The “Preview” must to be near “Add this task” with same background button color.
Thanks in advance.
|
|
2603 | Backend/Core | Bug Report | Very Low | Psi XMPP client (19-04-09) | Waiting on Customer | |
| | | 21.04.2020 | 25.09.2020 |
Task Description
From: https://groups.google.com/forum/?hl=en#!topic/flyspray/jC5BBQ1XiQo
19-04-09 // More one year ago.
On https://www.flyspray.org/ On https://www.flyspray.org/devel/team/
Replace : - https://www.psi-im.org/ → https://psi-im.org/
→ Remove the WWW.
|
|
2600 | Backend/Core | Information | Low | Error #17 when selecting a project | Unconfirmed | |
| | | 31.03.2020 | 31.03.2020 |
Task Description
When I am at the global projects page at index.php?do=admin&area=editallusers and now select a project from the dropdown menu at the top right, I get an error
FEHLER #17: Ungültiger Projektmanager-Bereich!
(according to the the translation area this is key 813: error17 Invalid PM area.)
If I select the project again, the projects start page will be shown correctly.
|
|
2599 | Backend/Core | Information | Low | add post request on new task creation | Unconfirmed | |
| | | 30.03.2020 | 12.04.2021 |
Task Description
I’m currently using flyspray 0.9.9.7
I want to make a little integration of our flyspray installation into slack. I want make a POST request when a “new task is created”
Any experiment guy can help here ? 1. Where is the best place to achieve this quickly as “hack hardcode” 2. Im not php developer, is there any php lib in flyspray todo quick POST request without installing any additional lib.
|
|
2588 | Backend/Core | Bug Report | Low | ps_files_cleanup_dir: opendir(/tmp/.priv) failed: Permi... | Unconfirmed | |
| | | 18.12.2019 | 05.02.2021 |
Task Description
Sometimes comes this message with a lot of backtrace log. If you are reporting a bug please provide as much information as possible to help understand and reproduce the problem:
Did you installed an official release or did you used an inoffical docker?! Official download flyspray-1.0-rc9
mysqlnd 5.0.12-dev Linux 64bit PHP Version 7.2.25
Steps done to create the problem: Wait some weeke and edit a ID.
Experienced behavior:
[18-Dec-2019 13:19:41 Europe/Berlin] PHP Notice: session_start(): ps_files_cleanup_dir: opendir(/tmp/.priv) failed: Permission denied (13) in /var/foo/htdocs/flyspray/includes/class.flyspray.php on line 1006
[18-Dec-2019 13:19:41 Europe/Berlin] PHP Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at/var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/includes/class.flyspray.php on line 1006
[18-Dec-2019 12:19:41 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/index.php on line 96
[18-Dec-2019 12:19:41 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/index.php on line 97
[18-Dec-2019 12:19:41 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/includes/class.csp.php on line 76
[18-Dec-2019 12:19:41 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/includes/class.csp.php on line 80
[18-Dec-2019 12:19:41 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/foo/htdocs/flyspray/includes/class.flyspray.php:1006) in /var/foo/htdocs/flyspray/includes/class.csp.php on line 82
|
|
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.
|
|
2586 | Backend/Core | TODO | Low | PHP7.4 | New | |
peterdd | 1.0-rc10 | | 12.12.2019 | 13.04.2021 |
Task Description
PHP 7.4 is out now and a few things should be done to make Flyspray work well with it. Nothing really breaks, but a view deprecation warnings should be fixed.
Flyspray source itself: Just a few new notices, most are yet fixed in the master branch.
Watching the PHP7.4 compatibility of dependencies defined by composer.json:
ADOdb/ADODb: 5.21 for PHP 8 done
swiftmailer/swiftmailer: We still use 5.* branch, so either do quickfix for a notice in a fork or upgrade/rewrite our integration to the 6.* branch. 6.* is PHP7+, so stay with 5.* branch for now. If Swiftmailer does not fulfill requirements, consider switching to PHPMailer for FS1.1+
ezyang/htmlpurifier: 4.13 OK
thephpleague/oauth2-client: unknown, we still use 0.13, last real source change was Nov 2018, to upgrade requires rewrite of integration into Flyspray and there is low demand for OAuth2.
dapphp/securimage: seems to be OK, but not maintained anymore (we could patch it if there occur problems in future)
jamiebicknell/sparkline: OK, but probably obsolete for us in future due
still annoying problems with our github/travis tests (problem of travis, not sparkline itself)
better solution (interactive hover infos, scales, screen size adaptive) by Flyspray source planned
|
|
2582 | Backend/Core | Information | Low | How to reach internal windows share (was: Internal URL) | Unconfirmed | |
| | | 04.11.2019 | 05.11.2019 |
Task Description
I have installed flyspray on an internal server and have problems with the renaming of internal links.
For example: I want to put this link in the comment section. \\192.168.200.5\Folder\example.docx
it shows the link correct, but when you hover over the link it shows: file://192.168.200.5/Folder/example.docx
And on clicking on it, of course I can´t access the file, because it´s trying to open an external link. I dont want it to be renamed from ‘\’ to ‘/’.
Can somebody help me please.
I tryed to find it in the sourcecodes, but I have almost no experience in PHP.
Thank you!
|
|
2575 | Backend/Core | Feature Request | Low | ability to view and reset Flyspray default settings | New | |
| | | 19.09.2019 | 19.09.2019 |
Task Description
Motivation
Over the years the count of possible Flyspray configuration options has grown. Meanwhile there are ~60 global Flyspray settings stored in the prefs database table in contrast to only 14 entries of the 0.9.7 (not 0.9.9.7!) version from around 2005. But each configuration setting might add a little to the feeling of overwhelming when there are too much switches, buttons, checkboxes and probability of a misconfiguration raises due misunderstood or overseen settings.
But Flyspray still aims to be easy to use and work with while being accurate and customizable.
Proposal
Having a way to view the description and default value of each option would probably give people administrating a Flyspray installation a better understanding of each setting and confidence in making good decisions for their use case.
With the flyspray-install.xml file within the setup folder we yet have an elegant solution that is waiting to unlock its power!
Unfortunately the setup/ folder requires (until now at least) to be removed after install or upgrade. So we need a way to keep the flyspray-install.xml of the installed version. A trivial way would be to copy it to the include/ directory after any install or upgrade, but also other solutions could be.
Keeping the flyspray-install.xml could making following features easier:
Reading default value of prefs setting. That could be shown for example as css title attribute /tooltip for each setting in the matching admin forms.
Reading default value and field description of any table field using the descr feature of ADOdb xmlschema03.
Comparing the real database structure with the table structures in flyspray-install.xml . This could be useful if someone extended or fiddled with database/tables to compare with official Flyspray releases. Or for developers to compare if an database upgrade went well and as intended.
Having the description of a setting or database field contained within the flyspray-install.xml is good at one place and the information is not spread around like in an external manual/wiki that maybe get unmaintained, not in sync with the application or get even lost over the years.
Using the xml format makes a migration easier (in a broader context, to Flyspray or away from Flyspray)
Using the descr tag could be used to hold information which field(s) of a database table is/are foreign key field(s) pointing to primary key field(s) of another table, even if ADODB xmlschema03 does not support it yet. Would generating database schema diagram directly from flyspray-install.xml possible. (instead of manually painting it that gets outdated when structure changes)
Things to take care:
ADOdb and xmlschema03 does not handle table comments and field comments yet. The descr tag so is there only used when looking into the .xml file, but it does not appear in the real database schema. To make this happen, there is a good portion of contribution to the ADOdB project required (making pull request, but also get them reviewed, tested, accepted and released with a ADOdb stable release)
ADOdb xmlschema03 does not define or handle foreign key constraints. Adding that would require a substantial amount of constribution to get it working reliable for all supported databases that could use foreign key constraints.
limits of table comment length, field comment length depend on database type and database version
|
|
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.
|
|
2561 | Backend/Core | Feature Request | Medium | ability to limit assignee permissions (was:User without... | Confirmed | |
| | | 05.08.2019 | 08.08.2019 |
Task Description
I gave a role the following privileges:
A user with the assigned role can still modify the task descriptions and task details. (I want that user to only be able to add comments.) I think there is a bug. Is there a fix or walk around? Thx
|
|
2559 | Backend/Core | Bug Report | Low | a duplicate close accepted even when missing comment/ r... | New | |
peterdd | | | 29.07.2019 | 29.07.2019 |
Task Description
Closing a task with selected close reason duplicate should warn when there is no comment or FS # id is given in the close comment text field.
The task is closed as duplicate without any further notice. The information to which task it is duplicate or a description (if the problem is logged/handled outside Flyspray) is lost.
Possible solutions
Frontend hints
variant F1 (soft): When duplicate as close reason is selected, a placeholder attribute in the close comment text field could be shown/updated. (maybe as ‘css only’ possible)
variant F2 (harder): Deny sending the form if duplicate selected, but comment text field is empty. and shows warning info. (javascript required, nojs browsers still send form.)
variant F3 (hard): Deny sending the form if duplicate selected and no task id detected in comment text field. and shows warning info. (javascript required)
Backend deny
variant B1 (soft): When request wants close a task with duplicate reason and (cleaned) comment string is empty, deny closing the task and give feedback to user why it was denied.
variant B2 (hard): It requires detecting a task id in the comment field and the first detected task id is taken for referencing as ‘is duplicate of’. Limitation of this is that the duplicate could be also a ticket or something of a complete other system.
|
|
2536 | Backend/Core | Feature Request | Medium | store session in Flyspray database | New | |
| | | 21.01.2019 | 15.03.2019 |
Task Description
Currently the sessions are stored by the webservers default settings.
Having this sessions under control by Flyspray by storing it in the database has following advantages:
Allows handling of all sessions of a user by Flyspray.
Providing a session management for each user. The user can see on which devices he is currently logged in and could also force a logout on selective devices.
A forced logoff of all or some user sessions is easy implementable for admins.
Statistics about how many users and who is logged in. (user status: hide always, online, offline, do not disturb, ..)
Could make onpage-notifications easier to implement.
.. ?
Disadvantages:
A potential unknown security bug in Flyspray that could lead to reading a session db table could leak informations like who is currently online/active and make further attacks more focused or makes session takeover easier.
.. ?
|
|
2535 | Backend/Core | Feature Request | Low | new optional Flyspray setting: add new users automatica... | New | |
| | | 16.01.2019 | 21.01.2019 | |
|
2534 | Backend/Core | Feature Request | Low | Private projects | Unconfirmed | |
| | | 16.01.2019 | 18.01.2019 | |
|
2527 | Backend/Core | Bug Report | Low | Database Check »Your mysql supports full utf-8 since 5.... | Unconfirmed | |
| | | 05.01.2019 | 05.01.2019 | |
|
2522 | Backend/Core | Feature Request | Low | email vs username login issues | Researching | |
| | | 31.10.2018 | 02.11.2018 | |
|
2491 | Backend/Core | Bug Report | Low | group member links if project manager but not admin | New | |
| 1.0 | | 01.09.2018 | 01.09.2018 | |
|
2484 | Backend/Core | Information | Low | Increase min. version of PHP requirement | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2482 | Backend/Core | Information | Low | Protect issues by default | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2481 | Backend/Core | Information | Low | Move to MVC | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2480 | Backend/Core | Information | Low | Better file organization | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2479 | Backend/Core | Information | Low | User table seems really complex | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2477 | Backend/Core | Information | Low | old style MySQL extension is abandoned .. | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2476 | Backend/Core | Information | Low | Guzzle/Guzzle is abandoned, should use library that's s... | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2466 | Backend/Core | Information | Low | How to run under https | Unconfirmed | |
| | | 03.06.2018 | 02.12.2018 | |
|
2454 | Backend/Core | Bug Report | Low | PHP warning in admin edit user area | New | |
| | | 15.01.2018 | 15.01.2018 | |
|
2453 | Backend/Core | Bug Report | Medium | validate category before storing a new task | New | |
| 1.0 | | 14.12.2017 | 14.12.2017 | |
|
2451 | Backend/Core | Feature Request | Low | Mod: blank Category - user must chose before pressing A... | Confirmed | |
| | | 08.12.2017 | 14.12.2017 | |
|
2449 | Backend/Core | Bug Report | Low | Unexepted exception on smtp gmail send | Unconfirmed | |
| | | 29.10.2017 | 10.01.2018 | |
|
2448 | Backend/Core | Bug Report | Low | error message in eventlog reports | Unconfirmed | |
| | | 26.10.2017 | 29.10.2017 | |
|
2447 | Backend/Core | Feature Request | Medium | Allow notifications when a new task is created | Unconfirmed | |
| | | 26.10.2017 | 29.10.2017 | |
|
2441 | Backend/Core | Bug Report | Medium | refactor dokuwiki image tags | New | |
| | | 15.09.2017 | 15.09.2017 | |
|
2440 | Backend/Core | Feature Request | Low | Option to disable tag feature | New | |
| | | 15.09.2017 | 15.09.2017 | |
|
2439 | Backend/Core | Feature Request | Low | Clone a Project | New | |
| | | 15.09.2017 | 15.09.2017 | |
|
2436 | Backend/Core | Bug Report | Low | dokuwiki renderer creates nonunique html-id for h1,h2,h... | New | |
| | | 02.08.2017 | 02.08.2017 | |
|
2435 | Backend/Core | Information | Low | Max attach a file | Unconfirmed | |
| | | 18.07.2017 | 18.07.2017 | |
|
2430 | Backend/Core | Feature Request | Low | User dependency on project | Unconfirmed | |
| | | 16.03.2017 | 20.03.2017 | |