|
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 | 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
|
|
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
|
|
2602 | Documentation | Feature Request | Low | https://github.com/flyspray/flyspray instead of https:/... | Waiting on Customer | |
| | | 21.04.2020 | 09.10.2020 |
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.
|
|
2609 | User Interface | Feature Request | Low | Add an Effort Description field | Maybe | |
| | | 07.05.2020 | 25.08.2020 |
Task Description
It would be nice to have a description field to put a brief note about the work done for a given effort item. This would help when using effort tracking for the purpose of making invoices to a client.
|
|
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.
|
|
2040 | Installer and Upgrader | Information | Medium | FS1.0 Release builds | Confirmed | |
| 1.0 | | 23.08.2015 | 17.04.2019 |
Task Description
The Flyspray 1.0alpha1 .zip file release unzips directly to the current directory.
.zip files from github unzip to it’s own directory (flyspray-master.zip unzips to flyspray-master/ ). This is a bit safer, because you cannot accidently mess your directory structure with it.
The release should contain the binary fontawesome files instead of linking to the external CDN. Removes one dependency/singlepointoffailure. How this can be configured for automation? included in Flyspray source now. 
document how a release is exactly created. (consistency, reliability, automation, knowledge sharing for maintainers see below  )
Get in contact with os distributions, that could add Flyspray releases to their repositories (*BSD, Linux distributions, ..) This repositories could add the dependencies like ADODB within the packages (.rpm, .deb,..)
Steps how to do a Flyspray release (since Flyspray 1.0 RC)
Edit includes/class.flyspray.php on github.com and set the correct version for the release there (remove the ' dev’ from the version string), commit as new branch e.g. 1.0-rc1
-
“Release” the Flyspray source on github when satisfied with layout
Run buildscripts for different php versions (see comments at FS#2040)
-
-
Test the created blobs on different servers too.
-
-
-
Send an email to the Flyspray mailing list
-
Maybe we can use this sequence as template on bugs.flyspray.org for releases?
|
|
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.
|
|
2085 | Text Rendering | Information | Medium | Enabling Color Coding options in CKEDITOR | Unconfirmed | |
| | | 30.10.2015 | 30.10.2015 |
Task Description
Hi
So I figured out that there are no color coding options (to set text color and background color) for text in the CKEDITOR. I did some changes to CKEDITOR to add those, however, once I submit the text, it does not retain the changes.
Is there a particular reason why these are not enabled in the first place?
I am thinking it would be good add these, so that we can make the important text pop-out to the users.
- Raju
|
|
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.
|
|
2221 | Installer and Upgrader | Information | Low | Notices on install with PHP7 | New | |
| 1.0 | 1 | 24.10.2016 | 24.10.2016 |
Task Description
Notice: Only variables should be assigned by reference in /*/setup/index.php on line 883
Notice: Only variables should be assigned by reference in /*/setup/index.php on line 949
|
|
2222 | Greek | Information | Very Low | Greek translation issues | Unconfirmed | |
| | | 24.10.2016 | 24.10.2016 |
Task Description
After completing the Greek translation I have a series of issues I want to report concerning mainly (but not limited to) the Greek languange.
I was thinking of opening a separate task for each one of them (note that they are all ultra low severity/priority) and adding them as sub-tasks to this one (or maybe as dependencies - or both).
I also request a Translations > Greek sub-category. I really have a lot of issues.
|
|
2324 | Backend/Core | Information | Low | Update composer.json | Unconfirmed | |
| | | 31.12.2016 | 31.12.2016 |
Task Description
...
symfony/event-dispatcher suggests installing symfony/dependency-injection ()
symfony/event-dispatcher suggests installing symfony/http-kernel ()
guzzle/guzzle suggests installing guzzlehttp/guzzle (Guzzle 5 has moved to a new package name. The package you have installed, Guzzle 3, is deprecated.)
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.
|
|
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 | ad post request on new task creation | Unconfirmed | |
| | | 30.03.2020 | 30.03.2020 | |
|
2600 | Backend/Core | Information | Low | Error #17 when selecting a project | Unconfirmed | |
| | | 31.03.2020 | 31.03.2020 | |
|
2612 | User Interface | Information | Medium | Restrict some projects to users | Waiting on Customer | |
| | | 19.08.2020 | 24.08.2020 | |