|
2559 | Backend/Core | Bug Report | Low | a duplicate close accepted even when missing comment/ r... | New | |
peterdd | | | 29.07.2019 | 29.07.2019 |
Task Description
Closing a task with selected close reason duplicate should warn when there is no comment or FS # id is given in the close comment text field.
The task is closed as duplicate without any further notice. The information to which task it is duplicate or a description (if the problem is logged/handled outside Flyspray) is lost.
Possible solutions
Frontend hints
variant F1 (soft): When duplicate as close reason is selected, a placeholder attribute in the close comment text field could be shown/updated. (maybe as ‘css only’ possible)
variant F2 (harder): Deny sending the form if duplicate selected, but comment text field is empty. and shows warning info. (javascript required, nojs browsers still send form.)
variant F3 (hard): Deny sending the form if duplicate selected and no task id detected in comment text field. and shows warning info. (javascript required)
Backend deny
variant B1 (soft): When request wants close a task with duplicate reason and (cleaned) comment string is empty, deny closing the task and give feedback to user why it was denied.
variant B2 (hard): It requires detecting a task id in the comment field and the first detected task id is taken for referencing as ‘is duplicate of’. Limitation of this is that the duplicate could be also a ticket or something of a complete other system.
|
|
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 |
|
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.
|
|
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.
|
|
2625 | User Interface | TODO | Low | avoid password manager popups in admin prefs area | New | |
peterdd | | | 10.02.2021 | 10.02.2021 |
Task Description
We must teach browsers not to use some input fields in the admin prefs area to offer to store it in their password manager.
Steps to reproduce:
Login with Firefox as admin into Flyspray. (Maybe other browsers behave same)
Go to admin prefs area (top right gear icon)
Click link somewhere else (so leaving admin prefs page)
Firefox browser pops up password manager as it detected some password input fields on admim prefs setting page. But in this case this is not wanted.
Either by using different input field names where the browser does not assume it is a login password field or find input field attribute to tell them.
auto-complete="off"
is not working anymore in browsers for password fields.
webbrowser: Firefox 85.0.2
Popup probably triggered by the password fields for configuring Email and XMPP notification: smtp_pass and jabber_password input fields. Firefox heuristic is too stupid to detect that these are for server configuration, not user login fields!
Neither
autocomplete="new-password"
nor
autocomplete="one-time-code"
attribute helped.
Stubborn Firefox ..
|
|
2629 | Backend/Core | Bug Report | Low | activating history tab sends same request 2 times | New | |
| | | 11.03.2021 | 11.03.2021 |
Task Description
There should be only one request to
js/callbacks/gethistory.php when activating the History tab
The request is made:
on mousedown event
on click event
So holding down the tab sends the first request and releasing sends the second request.
|
|
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.
|
|
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
|
|
2654 | Backend/Core | TODO | Medium | PHP8.1 compatibility | New | |
| | | 19.10.2021 | 19.10.2021 |
Task Description
[ ] ADOdb xmlschema03 issues [ ] other warnings/notices
|
|
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.
|
|
1222 | Backend/Core | Feature Request | Medium | Workflow engine / Role-based State Transition Rules Eng... | Unconfirmed | |
| | 7 | 25.03.2007 | 05.05.2019 |
Task Description
I have been working with Eventum (http://www.mysql.org/downloads/other/eventum/) for quite sometime now and in contrast, I like Flyspray for its simplicity and practicality. But one thing I badly miss (and something that Eventum scores high) is a Workflow Engine. If not a sophisticated W.E., I (as an Admin / Manager) should be able define role-based state transition rules of the tasks reported in a particular project. For example, I should be able to implement the following scenario:
For a “Developer”, the subsequent tasks from various states. Likewise for other roles
“Developer” should not be able close out the bug reports. He/she can only flag them as implemented. The “Reporter” of the bugs or the “Manager” alone should be able to close out issues
..
.. it will go on like that 
This feature, in my opinion, is very crucial for corporate organizations to give a serious consideration to Flyspray.
|
|
1236 | User Interface | Feature Request | Low | Mark Issue As Verified or Unverifiable | Unconfirmed | |
| | 4 | 09.04.2007 | 18.07.2016 |
Task Description
Currently, the Vote functionality provides users a way to say "this issue is important to me". In addition to that functionality, it would be great for users to have a "Verify" ability on open issues; it would provide users a way to say "yes, this happens to me as well".
A "Verified" label would fit nicely right under "Votes", to the right of the label would be "Yes | No", each option being a link. After clicking Yes or No, or if unable to specify (lack of permissions), the text would display "Yes - # | No - # (% verification)" where '%' is the result of ((Yes/(Yes+No))*100).
This feature should not show up on all issues, though. It does not make sense to "verify" a feature request or todo item, for example. When defining task types, the administrator would specify if a type was "Verifiable" by checking a box in a column next to "Show".
If implemented, two great, mini extra features would be:
The ability for the administrator to set the number of "Yes" verifications an issue would need before it was elevated to the next priority, severity, or both (specified by the administrator).
The ability for the administrator to set the number of "No" verifications an issue would need before it was lowered to the previous priority, severity, or both (specified by the administrator).
Both settings should have an option to be incremental (priority / status increased every x verifications) or not (increases once, no matter how many verifications are received); an "Incremental" checkbox would do nicely. Also, a little "Enabled" checkbox next to both settings would be clearer than having zero act as the disable mechanism.
As with voting, a permission should exist to enable or disable this option for a user group. For larger projects, moderators tasked with verifying bugs could be given the permission whereas smaller projects may leave verifications up to the community.
Lastly, a way to send a notification once the number of "Yes" verifications reached a certain value would also be a great addition.
|
|
1481 | User Interface | Feature Request | Low | Diff visualisation | Unconfirmed | |
| | 1 | 04.05.2008 | 09.03.2015 |
Task Description
Flyspray should be able to render attached patches visually like, for example, Bugzilla: https://bugzilla.wikimedia.org/attachment.cgi?id=4807&action=diff
|
|
1491 | User Interface | Feature Request | Low | Custom task table columns for individual users | Unconfirmed | |
| 2.0 | 3 | 01.07.2008 | 01.10.2015 |
Task Description
Allow individual users to define custom views of the task tables much like the project manager can for the entire project; only on a user scale.
An option for the user to "use default" project settings should be possible and should be the default. Only pro users will change it to their needs, not the average reporter.
Interesting would be the possibility to change it dynamic on the tasklist view, not only on the myprofile setting page.
Open Question: Simple or complex implementation?
|
|
1518 | Notifications | Feature Request | Low | Show last date/time when a reminder was sent | Unconfirmed | |
| | | 15.11.2008 | 15.11.2008 |
Task Description
This information is already stored in the table "reminders" in field "last_sent". It might be helpful in some situations, if this date/time would be visible to the user on the reminder list, too.
|
|
1521 | Backend/Core | Feature Request | Low | Assignees should be able to see and create reminders fo... | Unconfirmed | |
| | | 22.11.2008 | 18.04.2009 |
Task Description
In version 0.9.9.5.1 (unfortunately I couldn't select this version in the dropdown list on the left), reminders can only be created and edited by Admins and Project Managers. I recommend to give Assignees the permission to create reminders for themselves. To minimize any programming impact, his may be done as part of the "edit own tasks" permission.
This topic has been reported by Engie as part of Bug #713 for version 0.9.8 as well: "Also it would be useful if a user could create reminder for himself." Although that bug is already closed ("fixed in devel"), this part is not yet solved in the current version.
|
|
1539 | Backend/Core | Feature Request | Low | Sitemap.xml Generation | Unconfirmed | |
| 2.1 | 1 | 12.01.2009 | 11.03.2015 |
Task Description
I would like the feature to have a sitemap.xml file be generated, say every xx days, set in the configuration.
|
|
1608 | Installer and Upgrader | Bug Report | Low | reserved characters cause database error after installa... | Unconfirmed | |
| 2.1 | | 07.10.2009 | 03.03.2013 |
Task Description
the installer does not check for reserved characters when writing to flyspray.conf.php, causing parse_ini_file() to return an invalid database password.
|
|
1612 | Backend/Core | Feature Request | Low | Allow Comments by anonymous Users | Unconfirmed | |
| 2.0 | 1 | 20.10.2009 | 17.01.2013 |
Task Description
I would love a option to allow anom users to write comments! Maybe with CAPCHA... I allow anom users to report bugs, but when I have a question to this bug, or the reporter wants to make a additions, he has to register...
I tried hacking it in the core: In the class.user.php at the end of the get_perms method I added: $this→perms[$proj_id]['add_comments'] = 1;
But I has nothing changed. The I removed the check if the user had the right to make a comment in the template file, now I have a comment field for everyone, but anom user get a error message saying, that they should enter a comment... I searched a lot in the core files, but I don´t find the point where the comment a written in the database... I would a great help if you could give at least a hint :)
Another thing i tried was changing the user contructor, that every user with a negative ID get the ID 2, witch is a special "anom" user. But then you could not log out, a the admin not in...
Here the link to my site: bugs.thekingdomofdarkness.de
|
|
1628 | Notifications | Feature Request | Low | Global Notification address | Unconfirmed | |
| 2.0 | | 25.02.2010 | 17.01.2013 |
Task Description
For a combination of archiving / "notify bot" reasons I have found it useful to have a single global notification address where all bug reports / updates / comments go.
In the past I've used this to automatically dump updates into a IRC / Jabber chat room as well as provide a way for a project manager (me) to keep an idea of the amount of activity. Please let me know if you have questions about this.
|
|
1670 | User Interface | Feature Request | Low | Assign Key-Shortcuts to form fields | Unconfirmed | |
| | | 04.12.2010 | 04.12.2010 |
Task Description
Forms should be submittable by using keyboard shortcuts. S for submit. Set-able via the accesskey attribute on HTML inputs.
|
|
1977 | Backend/Core | Bug Report | Low | Weird URL after closing task with reference | Unconfirmed | |
| | | 15.03.2015 | 18.03.2015 |
Task Description
On Mac OS Safari:
I just closed a task and wrote the following into the comment for closing:
"See also F.S.#.14" (of course without the points). When I then click the link in the comment box (below the task details) I'm redirected to: "http:/flyspray.stefan-herz%0Aog.tld/index.php?do=details&task_id=%0A14". No matter if #14 is closed or not. It worked with Firefox.
Any suggestions?
|
|
1983 | Backend/Core | Feature Request | Low | Export Roadmap as "Changelog" | Unconfirmed | |
| | | 21.03.2015 | 21.03.2015 |
Task Description
It's a little like "text version". So you could use this exported changelog within a new release.
I think good was:
Only resolved tasks ordered by date (but of course without displaying the date) and only public accessible tasks
Without task number ("FS#...")
A download function via button
|
|
1987 | API | Feature Request | Medium | REST API to get metrics from flyspray projects | Unconfirmed | |
| | | 29.03.2015 | 06.10.2015 |
Task Description
I need metrics for flyspray projects about a rest api. For example the count of issues for status, priority. I want use this values for my code analysis system http://www.sonarqube.org/ and other internal tools. It is possible to create a rest api with user authorization and only for metrics data?
|
|
2025 | User Interface | Feature Request | Low | Adding new tasks is too undiscoverable | Unconfirmed | |
| | | 09.08.2015 | 09.08.2015 | |
|
2042 | Backend/Core | Bug Report | Medium | function absoluteURI not using basedir and force_basedi... | Unconfirmed | |
| | 1 | 04.09.2015 | 01.10.2015 | |
|
2045 | User Interface | Feature Request | Low | need add option for can set default Severity and Priori... | Unconfirmed | |
| | 2 | 04.09.2015 | 04.09.2015 | |
|
2046 | User Interface | Feature Request | Low | Grouping in Task List | Unconfirmed | |
| | 1 | 04.09.2015 | 04.09.2015 | |
|
2047 | User Interface | Feature Request | Medium | Inserting images/screenshots from buffer | Unconfirmed | |
| | 1 | 04.09.2015 | 29.09.2015 | |
|
2048 | Backend/Core | Bug Report | Low | error when adding data containing national characters | Unconfirmed | |
| | | 09.09.2015 | 09.09.2015 | |
|
2049 | Backend/Core | Feature Request | Medium | Display login page or customizable page to anonymous us... | Unconfirmed | |
| | | 09.09.2015 | 04.04.2016 | |
|
2052 | Text Rendering | Feature Request | Low | Add Markdown syntax option for task descriptions | Unconfirmed | |
| | | 16.09.2015 | 08.08.2016 | |
|
2066 | Installer and Upgrader | Feature Request | Medium | Automated site update (like Wordpress) | Unconfirmed | |
| | 2 | 09.10.2015 | 10.10.2015 | |
|
2068 | Backend/Core | Information | Low | Deprecated: mysql_connect(): The mysql extension is dep... | Unconfirmed | |
| | | 10.10.2015 | 28.09.2020 | |
|
2083 | User Interface | Information | Low | Drag and drop tasks on roadmap | Unconfirmed | |
| | | 30.10.2015 | 30.10.2015 | |
|
2087 | Backend/Core | Information | High | See no Editor in Add New Task | Unconfirmed | |
| | 1 | 04.11.2015 | 05.11.2015 | |
|
2094 | Email | Bug Report | High | After Upgrade All Users Receive Notifications for All T... | Unconfirmed | |
| | 1 | 06.01.2016 | 13.01.2016 | |
|
2097 | User Interface | Bug Report | Medium | Url incorrect for view attachement | Unconfirmed | |
| | 1 | 16.01.2016 | 02.03.2016 | |
|
2107 | Authentication | Feature Request | Low | Support CAS Server Authenticate | Unconfirmed | |
| | | 02.03.2016 | 04.09.2019 | |
|
2112 | API | Bug Report | Medium | Assigned tickets aren't editable for lower privileged u... | Unconfirmed | |
| | | 31.03.2016 | 11.04.2016 | |
|
2116 | Email | Bug Report | Medium | Error with email notification | Unconfirmed | |
| | | 08.04.2016 | 15.04.2016 | |
|
2142 | Backend/Core | Bug Report | Low | Post-authenticate redirect does not make use of baseurl... | Unconfirmed | |
| | | 28.06.2016 | 01.08.2016 | |
|
2160 | Backend/Core | Bug Report | Low | Cannot "accept" PM close request if already closed | Unconfirmed | |
| | | 14.07.2016 | 14.07.2016 | |
|
2197 | Backend/Core | Bug Report | High | Change Time for everyone | Unconfirmed | |
| | | 21.08.2016 | 22.08.2016 | |
|
2198 | User Interface | Bug Report | Low | Multi-Select from tasklist offers options to those who ... | Unconfirmed | |
| | 1 | 22.08.2016 | 07.04.2021 | |
|
2200 | User Interface | Bug Report | Medium | Incomplete list of timezones available in the user pref... | Unconfirmed | |
| | | 26.08.2016 | 26.08.2016 | |
|
2201 | API | Bug Report | High | I got Fatal Error on the Github OAuth | Unconfirmed | |
| 1.0 | | 07.09.2016 | 09.09.2016 | |
|
2202 | Installer and Upgrader | Bug Report | High | Unable to upgrade | Unconfirmed | |
| | | 10.09.2016 | 11.10.2016 | |
|
2203 | Backend/Core | Information | Low | language files are in folder lang. But i can't change l... | Unconfirmed | |
| | | 21.09.2016 | 21.09.2016 | |