|
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.
|
|
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.
.. ?
|
|
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.
|
|
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
|
|
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
|
|
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.
|
|
2581 | User Interface | Feature Request | Low | replace bitmap icons of default theme | New | |
| | | 31.10.2019 | 05.04.2021 |
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
Dokuwiki toolbar fixed in devel for Flyspray 1.0-rc10
CKEditor: some modern CKEditor themes support color/dark mode, I will probably choose the moona-lisa theme as default.
|
|
2595 | Notifications | Feature Request | Low | Notifications to message platforms | Unconfirmed | |
| | | 05.03.2020 | 26.03.2020 |
Task Description
Is there any possible implementation in the future of a way to send new tasks and edited tasks in to discord or some messaging software like bots do, for example github bot will post new issues to a channel in discord so users can see and check up on things, especially for big projects which use these types of things and need a way to notify users of updates
|
|
2601 | Public Relations | Feature Request | Medium | http -> https missing redirection (19-04-09) | Assigned | |
Floelejudas_iscariote | | | 21.04.2020 | 25.09.2020 |
Task Description
From: https://groups.google.com/forum/?hl=en#!topic/flyspray/rAnks5y_uLk
19-04-09 // More one year ago.
There are not http → https redirections.
Only one example: - http://www.flyspray.org/docs/download/ is not redirected to https://www.flyspray.org/docs/download/
Note: It is better to have the main website in https://flyspray.org/.
http://www.flyspray.org/ + https://www.flyspray.org/ + http://www.flyspray.org/ must be redirected to https://flyspray.org/
|
|
2602 | Documentation | Feature Request | Low | https://github.com/flyspray/flyspray instead of https:/... | Researching | |
| | | 21.04.2020 | 13.04.2021 |
Task Description
From: https://groups.google.com/forum/?hl=en#!topic/flyspray/ItWHIOcu8wk
19-04-09 // More one year ago.
On the Flyspray homepage, no informations about https://github.com/flyspray/flyspray…
A lot of people think that the project is dead.
In the same time, can you change the https://github.com/Flyspray to https://github.com/flyspray ?
No lost, you can try it already works but it is not the default.
https://github.com/organizations/Flyspray/settings/profile → “Rename organization” and replace Flyspray → flyspray.
|
|
2606 | Database Queries | Feature Request | Low | duedate column sort asc in tasklist should put unset du... | New | |
| | | 02.05.2020 | 02.05.2020 |
Task Description
When a tasklist contains the duedate column and the user sorts by duedate ascending, the tasks that do not have a duedate set should not be listed first. Instead they should be listed after the tasks with duedates.
This way a user can see the task with the earliest duedate first instead of seeing a bunch of probably not so important tasks without duedates set.
|
|
2610 | User Interface | Feature Request | Low | Effort pop-up timer | New | |
| | | 07.05.2020 | 24.08.2020 |
Task Description
It would be terrific to have a small pop-up window that appears when you click to start tracking of an item. In the window could be:
This would help tremendously to remind a developer that he has one or more timers going in FlySpray.
If multiple timers are started, there could be multiple timer windows, each identified by the task name showing as part of the window (title bar or some text near the timer).
|
|
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.
|
|
2644 | Backend/Core | Feature Request | Medium | mark specific task as spam and punish user account who ... | New | |
| | | 08.07.2021 | 08.07.2021 |
Task Description
For users with administrative permissions, a moderation UI for spam tasks could be useful.
For other normal users a “mark as spam”-button (similiar to voting for a task) could help moderators to identify spam tasks.
Modify the spam task: Move to a hidden “Trash” project, replace summary and description with a default spam summary text end empty description.
The decision which kind of punishment of the account who created the spam depends on several things:
Is it a previously normal used account who got captured by a bad guy and suddenly started spamming?
Is it a fresh bot created account who tried creating many spam task to promote bad websites or do search ranking manipulation?
Is it a sneaky smart account who waits for the opportunity to offload spam in a subtile manner?
I think this is not so easy to automate without producing false positives, especially for a project without commercial interest and funding and no huge meta informations like Google or similiar data collecting corporation who have the ability to identify spam waves across the internet.
|
|
2649 | Installer and Upgrader | Feature Request | Low | Docker Container: is there a way to hook into the setup... | Unconfirmed | |
| | | 11.08.2021 | 27.08.2021 |
Task Description
Hi, in my free time of the last few days I begun developping a Docker container: https://github.com/blu-base/flyspray-docker. I derived it from a nextcloud docker container… For now, I limited my focus on an apache/debian buster container. I’d be happy to contribute the project to the official placeholder when it is ready.
Anyhow, in the entrypoint script, I use some environment variables to create the flyspray.conf.php from scratch. and would now need to populate the database. I understand i have to use the respective xml scheme as the setup/index.php does.
I am not experienced with php and database applications and would like to ask you for advice how to proceed efficiently.
Since the current setup is indented to be interactive in the browser, i would need to use a cli tool or a purposely-build php script to do the same task on the command line/on container startup. But this seems to me this would be code duplication and introduce more maintenance work.
Is it possible to hook into only some of the functions of the setup/index.php ?
What could be the next best approach to populate the db on first start?
Would it be a viable solution in trying to further modularize the setup - allowing to run parts on cli, like nextcloud’s occ tool?
|
|
2650 | Notifications | Feature Request | Low | notification content or fields dependent of user permis... | New | |
| | | 13.08.2021 | 13.08.2021 |
Task Description
From mailing list:
Hello,
I could not find if this was already posted before. We have this basic profile where customers only can create new tasks and receive some notifications when the status or details change. The idea is that they do not see the comments, we want to use them for internal communication. The think is that we just realized that they can not see the comments when they login but they receive them as notifications by email!
We want this notification for the admin users involved in the task but not for the customers. Is there a way to correct this behavior?
Thanks, Manu
|
|
2656 | Backend/Core | Feature Request | Low | keep link parameters for new task if not yet logged in | New | |
| | | 24.11.2021 | 24.11.2021 |
Task Description
When there is a link to the new task action from another site to a Flyspray installation and the user is not yet logged in, there is a redirect to the Flyspray start page losing the GET parameters.
Example:
https://bugs.flyspray.org/index.php?do=newtask&project=1&item_summary=blablabla%product_category=1
Or short example (nicer urls using .htaccess rules)
https://bugs.flyspray.org.de/newtask/proj1?item_summary=blablabla&product_category=1
After login the user should see the form with the original link parameters (if the user is allowed to and parameters are valid)
Currently the user must navigate to the correct project (if there are several) and the parameters from the origin link are lost.
|
|
2068 | Backend/Core | Information | Low | Deprecated: mysql_connect(): The mysql extension is dep... | Unconfirmed | |
| | | 10.10.2015 | 28.09.2020 |
Task Description
My version of PHP still shows deprecation warnings with flyspray.
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /var/www/flyspray.itiab.co.nz/htdocs/adodb/drivers/adodb-mysql.inc.php on line 353
Have all mysql.connect instances been removed? The connect will be removed from PHP soon and will cause problems.
|
|
2083 | User Interface | Information | Low | Drag and drop tasks on roadmap | Unconfirmed | |
| | | 30.10.2015 | 30.10.2015 |
Task Description
On the roadmap it would make life a lot easier if it was possible to drag and drop tasks into versions.
|
|
2087 | Backend/Core | Information | High | See no Editor in Add New Task | Unconfirmed | |
| | 1 | 04.11.2015 | 05.11.2015 |
Task Description
Hi,
I can’t see the Editor when I make new task. Also when I editing a exciting task.
See nothing to put any HTML code in it. Can you help me!?
I use this version: Flyspray 0.9.9.7
|
|
2203 | Backend/Core | Information | Low | language files are in folder lang. But i can't change l... | Unconfirmed | |
| | | 21.09.2016 | 21.09.2016 |
Task Description
In Admins Toolbox (Project preferences) i choose language de. The file exists in folder lang. But only english is shown. the same for french and so on. No really changes.
|
|
2208 | Backend/Core | Information | Low | Severity "medium" by default | Suspended | |
| | 1 | 27.09.2016 | 29.09.2016 |
Task Description
Hi, Where i can change severity and priority by default? I want change severity to “Medium” by default for group Basic I cant find this option in the Flyspray settings.
|
|
2210 | User Interface | Information | Low | Tasklist color for due date | Unconfirmed | |
| | | 12.10.2016 | 18.10.2016 |
Task Description
Hello,
I was wondering if there is a way to make the task more visible if it wasn’t completed due to the date that was selected by a user - let’s say a yellowish background in tasklist, just like the ones from custom css based on severity, but that will take color if the task has the due date passed.
|
|
2214 | Backend/Core | Information | Low | Changing status of task automatically | Unconfirmed | |
| | | 17.10.2016 | 06.11.2016 |
Task Description
Hello again,
I was wondering (again ) if the following scenario is possible for this bug tracking solution:
Our company uses this bug tracker mainly for helpdesk issues. However, our main users (except IT department) don’t seem to easily understand how to change the status of a ticket, they aren’t interested in doing that also.
So I would like to know if there is a way that we can develop some automatisation in changing the status automatically after customer replies to a message.
Let’s see the following scenario:
user A posts a new task
user B assigns himself (or other) to that specific task - the status automatically is changed to Assigned
user B replies to task by adding a comment - as a result of adding the new comment the task status should change automatically to Waiting for customer - without the need that user B to change the status
user A checks the comment from user B and decides to comment back to him. After pressing the Add comment button, the status should change automatically to Waiting for assignee
If the task is needed to have another status, the users can change them manually, but the automated part should be the waiting for customer and assignee.
On a basic algorithm it shouldn’t be hard (if user is logged in and is task owner, then after comment, task detail - status changing to id 4-5 from task-statuses table on mysql; if user is logged in and assigned to task, after adding comment change status 4-5 from task-statuses table).
I saw this thing on an otrs platform and it is quite ok for a simple user like ours.
Is there any way that we can personalise the flyspray in this way?
If yes, please give us an elaborate answer with what I should do for this to work.
Thanks in advance.
|
|
2220 | Backend/Core | Information | Low | One status with different color in tasklist | Unconfirmed | |
| | | 24.10.2016 | 03.11.2016 |
Task Description
Since we have a lot of tasks pending, our team leader wants a specific status (let’s say: Waiting for dispatch) to be marked with a green background in tasklist. Can you please help me to make this mod?
Thanks in advance.
|
|
2222 | Greek | Information | Very Low | Greek translation issues | Unconfirmed | |
| | | 24.10.2016 | 24.10.2016 | |
|
2324 | Backend/Core | Information | Low | Update composer.json | Unconfirmed | |
| | | 31.12.2016 | 31.12.2016 | |
|
2333 | Backend/Core | Information | Low | Set Default View on Login? | Unconfirmed | |
| | | 26.01.2017 | 27.01.2017 | |
|
2335 | Backend/Core | Information | Low | PDF Attachment does NOT View/Open in New Window/Tab | Unconfirmed | |
| | | 27.01.2017 | 27.01.2017 | |
|
2337 | Documentation | Information | Low | Flyspray Themes | New | |
| | | 02.02.2017 | 16.02.2017 | |
|
2339 | Email | Information | Low | Emailing issues | Unconfirmed | |
| | | 10.02.2017 | 10.02.2017 | |
|
2429 | Backend/Core | Information | Low | My tasks URL | Unconfirmed | |
| | | 09.03.2017 | 20.03.2017 | |
|
2432 | Database Queries | Information | Low | Delete tasks from all projects (like factory reset) | Unconfirmed | |
| | | 08.05.2017 | 10.05.2017 | |
|
2435 | Backend/Core | Information | Low | Max attach a file | Unconfirmed | |
| | | 18.07.2017 | 18.07.2017 | |
|
2444 | Installer and Upgrader | Information | Low | composer hits memory limits | New | |
| | | 04.10.2017 | 04.10.2017 | |
|
2466 | Backend/Core | Information | Low | How to run under https | Unconfirmed | |
| | | 03.06.2018 | 02.12.2018 | |
|
2476 | Backend/Core | Information | Low | Guzzle/Guzzle is abandoned, should use library that's s... | 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 | |
|
2479 | Backend/Core | Information | Low | User table seems really complex | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2480 | Backend/Core | Information | Low | Better file organization | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2481 | Backend/Core | Information | Low | Move to MVC | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2482 | Backend/Core | Information | Low | Protect issues by default | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2484 | Backend/Core | Information | Low | Increase min. version of PHP requirement | Unconfirmed | |
| | | 10.08.2018 | 10.08.2018 | |
|
2498 | Translations | Information | Low | Apply variable in language keys to push the local site ... | Unconfirmed | |
| | | 18.09.2018 | 02.11.2018 | |
|
2521 | Email | Information | Low | TLS email with self-signed certificate doesn't work, "C... | Unconfirmed | |
| | | 31.10.2018 | 03.11.2018 | |
|
2524 | Email | Information | Low | SMTP Mailer doesn't accept custom ports | Unconfirmed | |
| | | 05.11.2018 | 27.11.2018 | |
|
2545 | User Interface | Information | Low | Can't delete system wide 'Task Statuses' | Unconfirmed | |
| | | 20.04.2019 | 05.05.2019 | |
|
2551 | Authentication | Information | Low | LDAP/AD integration | Unconfirmed | |
| | | 15.05.2019 | 04.09.2019 | |
|
2582 | Backend/Core | Information | Low | How to reach internal windows share (was: Internal URL) | Unconfirmed | |
| | | 04.11.2019 | 05.11.2019 | |
|
2599 | Backend/Core | Information | Low | add post request on new task creation | Unconfirmed | |
| | | 30.03.2020 | 12.04.2021 | |