|
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!
|
|
2581 | User Interface | Feature Request | Low | replace bitmap icons of default theme | New | |
| | | 31.10.2019 | 07.12.2019 |
Task Description
I played with adding a dark mode color theme to the default CleanFS theme.
To make the dark theme just simple exchange some colors, the bitmap icons should be replaced with alternatives.
Easiest would be using the fontawesome font icons as Flyspray still uses them and they can simply get a css color assigned.
Examples
caret of tasklist
the ‘select all’ icon of tasklist, but also used at some more locations.
some icons in the Flyspray main toolbar (Overview, Tasklist, Event log, ..)
the black calendar icons for date selects
maybe the file type icons for attachments
Editors
|
|
2577 | User Interface | Feature Request | Very Low | distinguish between anonymous reporter and deleted user | New | |
| | | 18.10.2019 | 18.10.2019 |
Task Description
When a user is deleted from Flyspray, their opened tasks, closed task and task comments are then shown as Anonymous Submitter, the same way as anonymous reporters (not really anonymous, just that user does not have login account, but usually their email address is stored within that task data).
Currently just the entry from users table are deleted when a user is deleted. Their internal user_id integer is still within tasks and comments fields, and maybe some other tables too. So there is not a ON DELETE SET NULL rule or something like that applied. As it is just an autoincremented number by the system, this is not personal data imho and should be no problem for GDPR, but gives Flyspray the ability to distinguish between anon reporters and deleted users. Well, we could also look if there is an email address within task table entry for notification of anonymous reporter, but there are also tasks possible that have no user_id nor an email address.
It might by useful to present that information differently like deleted user or showing the info differently like icon + title-tooltip with explanation.
Also interesting what happens with mentions of a deleted username in a comment or task description. (see FS#2322)
The user isn’t in database, but deleting that now gone user should not modify tasks or comment where that username was mentioned I think. But what if another user registers under that now gone username? In that case that new user would inherit that mentions. Probably we can ignore that edge case as there will be not much things will happen with an old mention in old tasks/comments.
|
|
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
|
|
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 |
|
2568 | Documentation | Bug Report | Medium | [MANUAL] a missing image in "Understanding Permissions:... | Unconfirmed | |
| | | 01.09.2019 | 02.09.2019 |
Task Description
In the page http://www.flyspray.org/manual/group_permissions/ , it is written
Shown is an image of the permissions page for the Flyspray project’s Contributors group
but there is no image in there.
I can think of two ways of dealing with that I guess:
add an image
remove the sentence
What do you think?
|
|
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
|
|
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 ..
|
|
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.
|
|
2552 | Email | Bug Report | High | Email TLS error (was 'Mail Adress encryption') | Unconfirmed | |
| | | 30.05.2019 | 31.05.2019 |
Task Description
Official release
Steps done to create the problem: Insert correct (tested with gmail) data into the notification tab and click on “Test”
SSL and TLS are checked.
Expected behavior: Send test email and confirm it.
Experienced behavior: Following error message
Error message: Warning: stream_socket_enable_crypto(): Peer certificate CN=`*.netcup.net’ did not match expected CN=`mail*.netcup.net’ in /var/www/vhosts/.netcup.net/httpdocs/**/flyspray/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php on line 103 Completely unexpected exception: Unable to connect with TLS encryption This should never happend, please inform Flyspray Developers
|
|
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.
|
|
2550 | Email | Bug Report | Low | Exception handling sending email notification | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
Someone reported this:
Today i tried to report an issue about xxx on the xxx (namely xxx) and the following error message has been displayed:
Completely unexpected exception: Expected response code 250 but got code “451”, with message “451 Error in writing spool file " This should never happend, please inform Flyspray Developers
The issue itself has been created though.
|
|
2549 | User Interface | Bug Report | Low | Oauth register template always shows "Username already ... | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
RC9 running on CentOS LAMP stack
Steps done to create the problem: Set up google as an oauth provider. Have a user click “Sign in with Google” in the login box. User connects their account with Flyspray. Google redirects the user back to Flyspray The return screen (on flyspray) asks for a username.
Expected behavior: No warning about duplicate username should be shown on initial page load since no username was entered yet
Experienced behavior: A warning about the username being already taken is shown.
It appears there is no logic for showing or hiding that warning in register.oauth.tpl
(It would be great if flyspray was able to just use the email as a username to make the UX even better/simpler.)
|
|
2548 | User Interface | Feature Request | Low | CSS grid layout for task details page type | New | |
| | | 05.05.2019 | 05.05.2019 |
Task Description
Layouts from 320 pixel mobile portrait, tablet sizes and up to 4k monitor landscape mode using
@media queries
Mockups required not only for different sizes, but also different project configurations, user permissions, and task relations.
Should look ok whatever project configuration is done or how weird a task description is.
On wider screens the comments could be beside the task description for instance. Or some tabs or menus could be shown directly instead of grouping in the tabs.
|
|
2545 | User Interface | Information | Low | Can't delete system wide 'Task Statuses' | Unconfirmed | |
| | | 20.04.2019 | 05.05.2019 |
Task Description
From the ‘Task Statuses’ menu, when in the global project, the ‘delete’ cases are grayed out, preventing me from deleting them.
This is a problem for me because I would like to only have project specific statuses and I would like to name one of those statuses ‘Assigned’.
For now, I got around it renaming the system wide ‘Assigned’ status.
|
|
2544 | Email | Bug Report | Low | Error when registering new account | Unconfirmed | |
| | | 23.03.2019 | 23.03.2019 |
Task Description
I installed the developer edition.
mysql Ver 14.14 Distrib 5.7.25, for Linux PHP 7.2.15-0ubuntu0.18.04.1 Ubuntu 18.04.2
Admin settings → Allow users to register and send conf. email.
I DID set up email settings thru google and sent a test email. it did work.
After logging out, I tried to register a new account. I filled in details and got the following error: Completely unexpected exception: Expected response code 250 but got code “530”, with message “530 5.7.0 Must issue a STARTTLS command first. u13sm3937813iog.80 - gsmtp " This should never happend, please inform Flyspray Developers
Obviously, the confirmation email was never sent.
I am going to try to manually add a new user. Will update with outcome.
|
|
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 |
Task Description
When a Flyspray installation allows user self registration and has public but also more private projects, this feature could make the required configuration more clear:
In this case, keep the number of global user groups as low as possible and the global user group for basic or just registered users has only the ‘can login’ permission and nothing more. Because that only would be useless for new registered users, adding them also to a basic user group of a public project could be useful.
So my suggestion is:
A new optional global setting: Something like ‘default project user group’ (store 2 values: a project_id and a group_id). Validity of that setting must be checked during any user registration, so that project must exists now and at later time as also that project user group within that project. (’Checks’ of admin prefs)
So it would be like this for a new registered userA:
userA is in a basic default global user group: only login permission to handle his account registration (login, logout, user preferences, password forgotten)
userA is in project X default user group: some basic permissions you want allow for every (new) registered user in project X
project Y: all ‘allow anyone ...’-settings are unchecked, userA not in any user group of project Y
The setting is probably best put below the ‘Default global group for new users’ setting in the global admin prefs tab #userregistration as
Either: A dropdown list with all public projects with an existing user group and dependend on the selection the available basic project groups are loaded by ajax as a select list too.
Or: Only one dropdown list that contains a list of public projects with possible project user groups. Would not require extra ajax calls and is maybe enough because we could exclude project groups that have project manager permission or such configuration nobody would allow new registered users.
no default project user group
public projectA - simple user groupA1
public projectA - simple user groupA2
public projectB - simple user groupB
public projectC - simple user groupC
This idea could be enhanced further (put the new user to multiple public projects when he registers or let user choose from public allowed projects during registration process), but lets start simple.
|
|
2534 | Backend/Core | Feature Request | Low | Private projects | Unconfirmed | |
| | | 16.01.2019 | 18.01.2019 |
Task Description
I would like to restrict certain projects from view from normal users (Basic group.) I couldn’t find out a way to do it. I could restrict them from viewing tasks, which is good, but it would be nice to hide the project entirely from the Overview screen.
|
|
2531 | Translations | Feature Request | Low | detect usage of translation keywords | New | |
| | | 10.01.2019 | 19.03.2019 |
Task Description
Some translation keywords of Flyspray are used at more than one code location.
To help translators doing the correct translations, it would help to show in what context a translation keyword is used. Especially when a keyword is used more than once.
As we have our own translation helper integrated into Flyspray, we could show a ‘translation keyword usage counter’ there and maybe show on request in which file a translation keyword is used.
It would also help to identify ‘abandoned’ translation keywords that are not used anymore by Flyspray source.
Also it would help to identify when a translation is used at more than one location with maybe different context.
I think we can use a regular expression and scan the whole Flyspray source for that. (and maybe database entries if there are places that have translation keywords stored - I don’t think so, but better check that too first than forget that case)
The regular expression should match that examples case insensitive for the translation keyword report:
L('report'
L("report"
eL('report'
eL("report"
but also ugly cases like
l( 'report'
or
El ( "report"
case insensitive.
But not for example
createURL('report'
|
|
2528 | User Interface | Bug Report | Low | New user registration doesn't check for duplicate usern... | Confirmed | |
| | | 05.01.2019 | 07.01.2019 |
Task Description
Steps done to create the problem: Visit https://bugs.flyspray.org/index.php?do=register in a private browser window (so you are logged out)
Put in an already taken username (e.g. Stefan or Stefan2)
Expected behavior: Username gets red and a note appears that username already is taken
Experienced behavior: Username gets green and registration of a new user proceeds with sending a notification mail with confirmation code. After putting in the confirmation code in provided page, user gets presented a “username is already taken, choose another” (where?) message, and has to re-start registration process from beginning and hopefully this time choose a not taken name.
|
|
2527 | Backend/Core | Bug Report | Low | Database Check »Your mysql supports full utf-8 since 5.... | Unconfirmed | |
| | | 05.01.2019 | 05.01.2019 |
Task Description
Steps done to create the problem: Access /index.php?do=admin&area=checks with a MySQL Version >= 5.5.3
Expected behavior: Flyspray tests for character set and displays »Your mysql supports full utf-8 since 5.5.3. You are using x.x.x and flyspray tables could be upgraded.« when database schema or one table isn’t set to utf8mb4 character set.
Experienced behavior: Flyspray always shows this note, even though character set is correct.
As far as I can tell from the source, a query gets executed to the database (and if I do that manually the result is “utf8mb4, utf8mb4_unicode_ci” for my database), but the result doesn’t get checket, the note is always shown (line 123)
|
|
2524 | Email | Information | Low | SMTP Mailer doesn't accept custom ports | Unconfirmed | |
| | | 05.11.2018 | 27.11.2018 |
Task Description
Did you installed an official release or did you used an inoffical docker?! Yeah MySQL 8.0.12, 7.2.9 on debian buster
Steps done to create the problem: Enter server:port at Mail-Settings
Expected behavior: smtp.example.com:customport would make use of the custom port
Experienced behavior: TLS Errors
if ($fs->prefs['email_tls']) {
$swiftconn = Swift_SmtpTransport::newInstance($fs->prefs['smtp_server'], 587, 'tls');
} else if ($fs->prefs['email_ssl']) {
$swiftconn = Swift_SmtpTransport::newInstance($fs->prefs['smtp_server'], 465, 'ssl');
} else {
$swiftconn = Swift_SmtpTransport::newInstance($fs->prefs['smtp_server']);
}
Should be changed to
$someTemporaryVariable = explode(':',$fs->prefs['smtp_server']);
if ($fs->prefs['email_tls']) {
$swiftconn = Swift_SmtpTransport::newInstance($someTemporaryVariable[0], $someTemporaryVariable[1] || 587, 'tls');
} else if ($fs->prefs['email_ssl']) {
$swiftconn = Swift_SmtpTransport::newInstance($someTemporaryVariable[0], $someTemporaryVariable[1] || 465, 'ssl');
} else {
$swiftconn = Swift_SmtpTransport::newInstance($someTemporaryVariable[0], $someTemporaryVariable[1] || 25);
}
|
|
2522 | Backend/Core | Feature Request | Low | email vs username login issues | Researching | |
| | | 31.10.2018 | 02.11.2018 |
Task Description
So, I’ve been away from Flyspray for more than a few years. When I tried to login to the Flyspray here, I was unable to login, because I don’t remember my username, and I was unable to retrieve my username, because there’s no function for that. I was *also* unable to re-register the same email address. SO, having an account system that requires both unique usernames and unique email addresses, but has no way of retrieving one from the other, doesn’t work out so well.
Suggestion: either use email as username, or add a function to retrieve username (perhaps along with password retrieval . . password retrieval would then have to take username -or- email, probably)
|
|
2521 | Email | Information | Low | TLS email with self-signed certificate doesn't work, "C... | Unconfirmed | |
| | | 31.10.2018 | 03.11.2018 |
Task Description
I use a personal email server with a self-signed certificate (i’m not sure if it’s possible to use my https certificate for that? i don’t even kind of understand what all I did to get this email server setup, and I don’t really want to mess with it... especially since my https certificate comes from Let’s Encrypt... so i might have to muck with the email server every 60 days ... not sure?) ..
anyway, when I try to connect to it with Flyspray, I get above the Test Email button, “Completely unexpected exception: Unable to connect with TLS encryption This should never happend, please inform Flyspray Developers”
Most systems have a way to override and accept an invalid cert, but I’m not seeing anything obvious about doing that with Flyspray. Does a function for this already exist, or do we need a way to do that? (alternatively, I would accept help in properly configuring my email lol)
|
|
2520 | Notifications | Feature Request | Low | Send a notification for a new task in slack integration... | Unconfirmed | |
| | | 24.10.2018 | 19.03.2019 | |
|
2499 | User Interface | Bug Report | High | Change recaptcha from using file_get_contents to Curl | Unconfirmed | |
| | | 18.09.2018 | 02.11.2018 | |
|
2498 | Translations | Information | Low | Apply variable in language keys to push the local site ... | Unconfirmed | |
| | | 18.09.2018 | 02.11.2018 | |
|
2496 | Email | Bug Report | Low | Notification Mail - Link to the task invalid when quick... | Waiting on Customer | |
| | | 13.09.2018 | 14.09.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 | |
|
2490 | User Interface | Bug Report | Medium | Reset Password's Username field has maxlength of 20 - t... | Confirmed | |
| 1.0 | | 01.09.2018 | 10.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 | |
|
2459 | User Interface | Feature Request | Low | Attachments on/off and max size setting in Admin Toolbo... | Unconfirmed | |
| | | 16.02.2018 | 03.03.2018 | |
|
2456 | User Interface | Bug Report | High | Missing GUI controls | Unconfirmed | |
| | | 09.02.2018 | 10.02.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 | |
|
2444 | Installer and Upgrader | Information | Low | composer hits memory limits | New | |
| | | 04.10.2017 | 04.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 | |