|
2049 | Backend/Core | Feature Request | Medium | Display login page or customizable page to anonymous us... | Unconfirmed | |
| | | 09.09.2015 | 04.04.2016 |
Task Description
Currently, if there are no public project, the anonymous users gets a blank page not very useful. It will be a good idea to have a global configuration parameter to display some customizable-page or maybe the login form instead.
|
|
2054 | Backend/Core | Feature Request | Low | Fields for csv export choosable like for task list | New | |
| 2.0 | | 17.09.2015 | 31.12.2017 |
Task Description
Currently the task list columns are used, which are choosed by admin or project manager for the task list view.
|
|
2059 | Backend/Core | Feature Request | Low | usage of github automated/webhook notifications | New | |
| | | 24.09.2015 | 24.09.2015 |
Task Description
We have no API yet for Flyspray.
But someone could write a simple php-file that can be called by a github.com auto notification, whenever:
Github.com provides the configuration of such notification for a possible target like
https://bugs.flyspray.org/api/github.php
or
https://bugs.flyspray.org/api/github.php?project=1
in the settings of a project.
What the file needs:
import some of the existing Flyspray classes from includes/
config or load the secrets that are provided by github.com in the setup for the automatic notification
check that secrets and more for authentication and authorization of requests coming from github.com
-
take actions on the results of that message parsing like making adding comment or modifying a task status
|
|
2063 | Backend/Core | Feature Request | Very Low | show closed/open usage count on do=pm&area=XXX | New | |
peterdd | | | 29.09.2015 | 25.03.2021 |
Task Description
Currently on
do=pm&area=cat
do=pm&area=version
do=pm&area=os
do=pm&area=resolution
do=pm&area=status
do=pm&area=tags
do=pm&area=tasktype
a count of usage in tasks is shown for every property.
Interesting would be if the counter shows the count for open/closed tasks on each row.
|
|
2096 | Backend/Core | Feature Request | Very Low | Add an option to force https | Maybe | |
| | | 16.01.2016 | 17.01.2016 |
Task Description
Can you add an option to force HTTPS ?
Thx.
|
|
2105 | Backend/Core | Feature Request | Medium | countermeasures for 'add task anonymous' spam | New | |
| | | 27.02.2016 | 27.02.2016 |
Task Description
Today I got first SPAM on bugtracker.
Question: Is it possible to enable CAPTCHA for anonymus task add?
Question 2: Is it possible to delete SPAM tasks.
|
|
2190 | Backend/Core | Feature Request | Low | enable move of a closed clask to other project without ... | Researching | |
| | | 06.08.2016 | 06.08.2016 |
Task Description
Problem: By replacing just the project_id of the closed task it is possible the task then has invalid field values within the target project.
Possible scenarios:
Ignore invalid values within the target project
Pro: Easy to do, an immidiatly revert back to the old project would “heal” the task properties.
Contra: may effect accuracy and reliability of other parts like searching, listing, statistic calculations
Silent change task field values to valid field values of the target project if necessary
allow user to modify the fields that must be changed so that every field of the task has valid values within the target project
allow user to modify the fields, fields or field select values that do not exists in target project will be automatically created.
???
|
|
2327 | Backend/Core | Feature Request | Low | visibility-option for private tasks | Unconfirmed | |
| | | 15.01.2017 | 17.01.2017 |
Task Description
We have some private Tasks in our FS-bugtracker to hide them from normal reporters. But we also have some external beta-testers in a betatesters-group and they should be able to see (and check) the private tasks without giving them a project manager status. So it would be good, if there is a switch in the group option to give specific groups the right to see private tasks.
|
|
2328 | Backend/Core | Feature Request | Medium | Add [key] support for each project instead of FS# | Unconfirmed | |
| | | 20.01.2017 | 10.02.2017 |
Task Description
Adding key support for each project instead of using the prefix FS#<task_id>
Let the administrator choose the key for project.
What’s a project key? It prefixes each task in the project
|
|
2346 | Backend/Core | Feature Request | Low | Custom css inheritance | Unconfirmed | |
| | | 20.02.2017 | 23.02.2017 |
Task Description
If i set up a custom css in the main FS settings the style doesn’t get applied to all nested projects. I have to set the css to all projects explicitly to get the stylings work on all project pages. Wouldn’t it be a good idea to first load the css set in the main dialog and after that load an additional css specified in the sub project? Then it would be possible to specify general stylings for all projects and project based stylings also.
|
|
2427 | Backend/Core | Feature Request | Low | allow hotlinking (direct links) to uploaded files | Unconfirmed | |
| | | 07.03.2017 | 09.03.2017 |
Task Description
Currently all attached files get renamed (like “screenshot331.png” → “attachments/14_72a4ca580abcdef69f60b1f”) and they could be downloaded only throught the php script (”/index.php?getfile=1234”) which requires that user must be logged in to view the file. It is not very convenient when you need to show a file to some person who is on mobile phone at the moment or using not a work computer. Also sometimes you might need to share a file with anyone without having them to register at your bug tracker.
I suggest you to add a checkbox like “create a direct link” when uploading a file, which will save the file with original name and extension but adding some random generated prefix (like “screenshot331.png” → “attachments/14_72a4ca580abcdef69f60b1f.screenshot331.png”).
However this poses a high security risk so there should be a list of allowed file extensions (e.g. “jpg,png,txt,pdf,doc,zip”) - only these files could be saved with the original extension. This list should be accessible by the main administrator only, thus the safest option would be storing it inside the “flyspray.conf.php”.
|
|
2430 | Backend/Core | Feature Request | Low | User dependency on project | Unconfirmed | |
| | | 16.03.2017 | 20.03.2017 |
Task Description
So, there would be great option if we can set permission to users to see and post only in specific opened projects in bug tracker.
Idea is, that user has all right to all projects, but in some cases we want that user can see only projects which is allowed and also to publish new tasks to only allowed projects.
In that case tasks overiew is locked and user must be logged in to see opened tasks.
|
|
2439 | Backend/Core | Feature Request | Low | Clone a Project | New | |
| | | 15.09.2017 | 15.09.2017 |
Task Description
There is a request for cloning a project on Flyspray mailing list:
Would be a very welcome features to have Project Templates for repetitive workflow. Any idea if its in the pipeline?
Thanks
Well, not yet.
The question is, how exactly you want that project clone.
Do you want just a rough copy of the project table entry? Thats quite easy and can even be done without programming or writing a line of SQL just by using PHPMyAdmin (or similiar Tools for PostgreSQL) and copy a row of the project table for example. See yellow marked project table on the right of the attached dbschema screenshot.
The other extreme is copying every project depending list table entries to new ones. This sure requires some programming, but not too hard to add this to Flyspray. (all yellow marked tables in the attached dbschema screenshot.
I attach a rough form mockup how could this could look like.
Possible solution
add a new file scripts/ folder for instance copyproject.php (check admin permission)
add a template file to themes/CleanFS/templates/copyproject.tpl
Set a link to that clone form page somewhere, for example on the toplevel page of a project (see screenshot)
Handle the adminuser (or add a clonepermission for that project manager usergroup) submitted form careful and savely either by includes/modify.inc.php (or like scripts/copyproject.php to keep it seperate from core)
The link to the clone form looks then ?project=123&do=copyproject
|
|
2447 | Backend/Core | Feature Request | Medium | Allow notifications when a new task is created | Unconfirmed | |
| | | 26.10.2017 | 29.10.2017 |
Task Description
The only (only!) feature that I have missing in Flyspray is an option to receive email notifications when a new task is created
I think that this could be in the profile of the user, and/or in the main configurations as “send a notification to the -group- (admins?) when a new task is created”
Thanks a lot! flyspray r00lz after all these years, never failed, no bugs, no hacks, fast and efficient! :)
A Happy user.
|
|
2451 | Backend/Core | Feature Request | Low | Mod: blank Category - user must chose before pressing A... | Confirmed | |
| | | 08.12.2017 | 14.12.2017 |
Task Description
Hello Peter,
I am interested in making the following mod:
When posting a new task, category should be blank by default, in order for the user that opens a new task to select that specific category. If he doesn’t select any task, when pressing Add this task button, FlySpray should display an error message saying that the Category hasn’t been specified.
Do you think this mod can be made with the current version? If so, do you mind if you help me a bit with the things that need to be modified?
Thanks!
|
|
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)
|
|
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.
|
|
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.
.. ?
|
|
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
|
|
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.
|
|
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.
|
|
1671 | Database Queries | Feature Request | Low | Ability to extract CSV, or Excel | Planned | |
| 1.1 devel | 3 | 18.12.2010 | 08.10.2017 |
Task Description
At work, we would need to be able to do extractions from the list of regular Flyspray tasks. Have you the ability to integrate this functionality into the interface later.
|
|
1985 | Database Queries | Feature Request | Very Low | For developers - testing with huge flyspray data sets | New | |
| | | 24.03.2015 | 16.03.2016 | |
|
2014 | Database Queries | Feature Request | Very Low | Add MS SQL Server as database backend | Maybe | |
| | 1 | 20.07.2015 | 30.07.2015 | |
|
2606 | Database Queries | Feature Request | Low | duedate column sort asc in tasklist should put unset du... | New | |
| | | 02.05.2020 | 02.05.2020 | |
|
1964 | Documentation | Feature Request | Low | On page documentation | New | |
| | | 11.03.2015 | 11.03.2015 | |
|
2602 | Documentation | Feature Request | Low | https://github.com/flyspray/flyspray instead of https:/... | Researching | |
| | | 21.04.2020 | 13.04.2021 | |
|
2305 | Greek | Feature Request | Very Low | Month names not translatable | Unconfirmed | |
| | 1 | 26.10.2016 | 11.03.2019 | |
|
2066 | Installer and Upgrader | Feature Request | Medium | Automated site update (like Wordpress) | Unconfirmed | |
| | 2 | 09.10.2015 | 10.10.2015 | |
|
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 | |
|
1510 | Notifications | Feature Request | Medium | Function to test mail configuration | Planned | |
| 1.1 devel | 3 | 29.10.2008 | 28.10.2015 | |
|
1518 | Notifications | Feature Request | Low | Show last date/time when a reminder was sent | Unconfirmed | |
| | | 15.11.2008 | 15.11.2008 | |
|
1628 | Notifications | Feature Request | Low | Global Notification address | Unconfirmed | |
| 2.0 | | 25.02.2010 | 17.01.2013 | |
|
1783 | Notifications | Feature Request | Medium | Create account for non-logged user automatically | Planned | |
| 2.0 | | 27.11.2012 | 07.03.2015 | |
|
2023 | Notifications | Feature Request | Low | Inform users if reminder is disabled in system settings | New | |
| | | 04.08.2015 | 04.08.2015 | |
|
2064 | Notifications | Feature Request | Low | Deadline Alert - so Flyspray can send notifications som... | Maybe | |
| | | 06.10.2015 | 02.12.2015 | |
|
2216 | Notifications | Feature Request | Low | Add slack integration (webhook) | Unconfirmed | |
| | 1 | 18.10.2016 | 25.10.2018 | |
|
2520 | Notifications | Feature Request | Low | Send a notification for a new task in slack integration... | Unconfirmed | |
| | | 24.10.2018 | 30.03.2020 | |
|
2595 | Notifications | Feature Request | Low | Notifications to message platforms | Unconfirmed | |
| | | 05.03.2020 | 26.03.2020 | |
|
2650 | Notifications | Feature Request | Low | notification content or fields dependent of user permis... | New | |
| | | 13.08.2021 | 13.08.2021 | |
|
2601 | Public Relations | Feature Request | Medium | http -> https missing redirection (19-04-09) | Assigned | |
Floelejudas_iscariote | | | 21.04.2020 | 25.09.2020 | |
|
2425 | Slovenian | Feature Request | Very Low | Translation: Slovenian | Confirmed | |
| | | 05.03.2017 | 05.03.2017 | |
|
2052 | Text Rendering | Feature Request | Low | Add Markdown syntax option for task descriptions | Unconfirmed | |
| | | 16.09.2015 | 08.08.2016 | |
|
2531 | Translations | Feature Request | Low | detect usage of translation keywords | New | |
| | | 10.01.2019 | 19.03.2019 | |
|
920 | User Interface | Feature Request | Low | Charts (gantt, severities, OSes, opened-closed, ...) | Researching | |
| 2.0 | 9 | 06.05.2006 | 07.04.2021 | |
|
1040 | User Interface | Feature Request | Low | Close Multiple Tasks at once | New | |
| 1.1 devel | 3 | 17.08.2006 | 01.10.2015 | |
|
1134 | User Interface | Feature Request | Low | add icon/image for each project | Planned | |
| 1.1 devel | 3 | 29.11.2006 | 09.03.2015 | |