|
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.
|
|
2544 | Email | Bug Report | Low | Error when registering new account | Unconfirmed | |
| | | 23.03.2019 | 23.03.2019 |
Task Description
I installed the developer edition.
mysql Ver 14.14 Distrib 5.7.25, for Linux PHP 7.2.15-0ubuntu0.18.04.1 Ubuntu 18.04.2
Admin settings → Allow users to register and send conf. email.
I DID set up email settings thru google and sent a test email. it did work.
After logging out, I tried to register a new account. I filled in details and got the following error: Completely unexpected exception: Expected response code 250 but got code “530”, with message “530 5.7.0 Must issue a STARTTLS command first. u13sm3937813iog.80 - gsmtp " This should never happend, please inform Flyspray Developers
Obviously, the confirmation email was never sent.
I am going to try to manually add a new user. Will update with outcome.
|
|
2545 | User Interface | Information | Low | Can't delete system wide 'Task Statuses' | Unconfirmed | |
| | | 20.04.2019 | 05.05.2019 |
Task Description
From the ‘Task Statuses’ menu, when in the global project, the ‘delete’ cases are grayed out, preventing me from deleting them.
This is a problem for me because I would like to only have project specific statuses and I would like to name one of those statuses ‘Assigned’.
For now, I got around it renaming the system wide ‘Assigned’ status.
|
|
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.
|
|
2549 | User Interface | Bug Report | Low | Oauth register template always shows "Username already ... | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
RC9 running on CentOS LAMP stack
Steps done to create the problem: Set up google as an oauth provider. Have a user click “Sign in with Google” in the login box. User connects their account with Flyspray. Google redirects the user back to Flyspray The return screen (on flyspray) asks for a username.
Expected behavior: No warning about duplicate username should be shown on initial page load since no username was entered yet
Experienced behavior: A warning about the username being already taken is shown.
It appears there is no logic for showing or hiding that warning in register.oauth.tpl
(It would be great if flyspray was able to just use the email as a username to make the UX even better/simpler.)
|
|
2550 | Email | Bug Report | Low | Exception handling sending email notification | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
Someone reported this:
Today i tried to report an issue about xxx on the xxx (namely xxx) and the following error message has been displayed:
Completely unexpected exception: Expected response code 250 but got code “451”, with message “451 Error in writing spool file " This should never happend, please inform Flyspray Developers
The issue itself has been created though.
|
|
2551 | Authentication | Information | Low | LDAP/AD integration | Unconfirmed | |
| | | 15.05.2019 | 04.09.2019 |
Task Description
Hi
Please advise if there are known issues when integrating Flyspray with Active Directory using LDAP.
|
|
2553 | User Interface | TODO | Low | intelligent accesskey shortcut helper dependent of OS, ... | New | |
| | | 06.06.2019 | 29.07.2019 |
Task Description
The HTML accesskey attribute feature is differently accessible dependent of operating system, web browser and web browser configuration, and users keyboard layout and user language.
By taking advantage of the User-Agent HTTP header value provided by default by web browsers, Flyspray could better know of what kind of keyboard and browser the user sits in front off and show the key combinations for the accesskey feature that best fits the users environment.
|
|
2554 | User Interface | TODO | Low | keyboard shortcuts help box should adapt to current pag... | New | |
| | | 06.06.2019 | 06.06.2019 |
Task Description
The shortcuts help infobox should adapt to the current page type.
So when in editing a task for instance, the n (next task) and p (previous task) shortcuts are not available for a good reason. Listing them there with same priority as other keys then is not helpful.
The simpliest solution is probably putting some if-statements depending on the $do variable into CleanFS/templates/shortcuts.tpl ..
|
|
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.
|
|
2560 | Backend/Core | Bug Report | Low | do not allow close task with reason duplicate referenci... | New | |
peterdd | | | 29.07.2019 | 29.07.2019 |
Task Description
So closing a task
FS#1
with
reason: duplicate
and close comment
FS#1
referencing to self should be detected to avoid such user mistakes.
|
|
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 |
|
2573 | Backend/Core | TODO | Low | add rel nofollow,ugc,.. settings | New | |
peterdd | | | 14.09.2019 | 15.09.2019 |
Task Description
Find a good configuration name just reuse relnofollow as used by dokuwiki
Find a good translation keyword for that config relnofollow
Find a good translation keyword for config description (title attribute)
Goes into prefs table as it is sitewide configuration.
As first implementation a simple checkbox should be ok. Should be on the tab with other spam handling stuff like captcha configuration.
Is enabled by default (1). Adapt setup xml files, upgrade procedure.
|
|
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
|
|
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
|
|
2582 | Backend/Core | Information | Low | How to reach internal windows share (was: Internal URL) | Unconfirmed | |
| | | 04.11.2019 | 05.11.2019 |
Task Description
I have installed flyspray on an internal server and have problems with the renaming of internal links.
For example: I want to put this link in the comment section. \\192.168.200.5\Folder\example.docx
it shows the link correct, but when you hover over the link it shows: file://192.168.200.5/Folder/example.docx
And on clicking on it, of course I can´t access the file, because it´s trying to open an external link. I dont want it to be renamed from ‘\’ to ‘/’.
Can somebody help me please.
I tryed to find it in the sourcecodes, but I have almost no experience in PHP.
Thank you!
|
|
407 | Backend/Core | Feature Request | Medium | Plugin system | Confirmed | |
| 2.0 | 14 | 04.12.2004 | 17.01.2013 |
Task Description
Everything is currently hard-coded. Create a plugin system that allows a module to be simply "dropped into" a plugins/ directory, enabled in the options, and have the plugin just work.
Possibilities might include alternative methods of notification, perhaps a documentation subsystem, or even simple things like voting for tasks.
The user should NOT have to edit existing Flyspray source code to make a plugin work.
|
|
1222 | Backend/Core | Feature Request | Medium | Workflow engine / Role-based State Transition Rules Eng... | Unconfirmed | |
| | 6 | 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.
|
|
1237 | Backend/Core | Feature Request | Medium | Allow Multiple Owners Per Category | Planned | |
| 2.0 | 7 | 09.04.2007 | 10.08.2015 |
Task Description
Currently, only one owner can be applied per category (at least, that's what the tooltip implies). The ability to add more than one user, a user group, or a mix of the two to a category would be ideal.
Often times, more than one programmer will work on and maintain a feature that cannot be divided into subcategories with the various programmers dispersed accordingly. In such cases, setting all such programmers as owners of the category is beneficial in that they will all receive notifications.
Also, having a parent category's owner receive alerts if no owners are specified for a sub-category benefits from this ability. I may have a "User Interface" group that has all of my UI developers in it; assigning the group to the "User Interface" root category means all relevant developers find out about a new issue that was not directed elsewhere.
One potential conflict does arise with another Flyspray feature. If "Auto-assign a task to the category owner" is enabled, care must be taken to assign no users or the first user to the task; personally, I would prefer no one being assigned and seeing the wording changed to "Auto-assign a task to sole category owners". Worst case scenario would be another option asking if no one or the first user would be assigned to a task in that instance; if a group is specified, the first user in the group would be chosen.
|
|
1510 | Notifications | Feature Request | Medium | Function to test mail configuration | Planned | |
| 1.1 devel | 3 | 29.10.2008 | 28.10.2015 |
Task Description
Add a button to test mail configuration before notifications is accpeted
|
|
1697 | User Interface | Feature Request | Medium | Detailed Due Date, SMS Notification, Deadline Warning N... | Unconfirmed | |
| | | 28.12.2011 | 06.10.2015 |
Task Description
Hi there,
I was looking for some issue management tool for the company I work for and Flyspray turned out to be almost perfect solution. I installed it easily and it works GREAT! As I said, this turned out to be almost perfect solution, and this is because it lacks some features that my company needs.
Away with needs of my company, I believe that these features will make Flyspray very interesting and more suitable for many small/medium companies.
Best regards,
Milan Vlajnic
|
|
1751 | Backend/Core | Feature Request | Medium | Default to show all in Event Log | Confirmed | |
| 1.1 devel | 1 | 20.06.2012 | 09.02.2016 |
Task Description
Just show me all events when I click the Event Log tab (limited to x number). If I want to filter the results down I’ll use the UI. Currently, I click Event Log and get no information. Then I have to build a query of what I want to see (every time!).
|
|
1753 | Backend/Core | Feature Request | Medium | Usergroup Restriction: Only View Summary | Confirmed | |
| 1.1 devel | 2 | 20.06.2012 | 27.06.2016 |
Task Description
I was really impressed with Flyspray and about to use it as our bug tracker, but then I discovered quite a big problem. You can't restrict users from seeing full task details.
I would really love the ability to let them only see the summary. My reason being is that I'm needing a bug tracker for my game, and bugs reported can be easily abused, and will be abused, if people can just read bug reports and see how to replicate them.
The reason I don't like just unchecking the "View Tasks" option, is because they wont be able to see if there is already a task about the bug, so we would just get flooded with duplicate reports on the same bugs.
|
|
1783 | Notifications | Feature Request | Medium | Create account for non-logged user automatically | Planned | |
| 2.0 | | 27.11.2012 | 07.03.2015 |
Task Description
Hi, is there function in FS (0.9.9.7) wchich allow unregistered user automatically create account? FS is accessible only for our workers.
It would be sth like that: 1. Non-logged user creates ticket. 2. He type his e-mail (user_name@company.pl). 3. FS creates account for that user: a. user's login: user_name b. user's password: <generated by FS> 4. User's login and password'll be send on e-mail which was typed in e-mail field.
Is is possible to do it?
|
|
1791 | Backend/Core | Feature Request | Medium | Ability to merge version, OS, etc | Suspended | |
| | 1 | 12.12.2012 | 12.01.2017 |
Task Description
For example, say I no longer want 1.1, 0.9.9.8, 1.0.0, etc. So want to merge them all into one version 1.0. Same goes for OS, and others
|
|
1856 | Backend/Core | Bug Report | Medium | Wrong timezones | Researching | |
| | 2 | 27.03.2013 | 06.03.2015 | |
|
1861 | Backend/Core | Bug Report | Medium | Login-Page should redirect after login to the page, the... | Confirmed | |
| 1.1 devel | 1 | 12.04.2013 | 09.07.2018 | |
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 | |
|
1882 | Email | Bug Report | Medium | Error with email notification | Planned | |
| 2.0 | | 22.12.2013 | 08.04.2016 | |
|
1950 | User Interface | TODO | Medium | Solve confusing Flyspray group settings vs Project grou... | Confirmed | |
| 1.0 | | 07.03.2015 | 11.11.2015 | |
|
1960 | Backend/Core | Bug Report | Medium | foreign key relations between versions and tasks | New | |
| | | 09.03.2015 | 13.08.2015 | |
|
1980 | User Interface | Feature Request | Medium | Tasklist - PDF Export | Maybe | |
| 2.0 | | 19.03.2015 | 26.05.2016 | |
|
1987 | API | Feature Request | Medium | REST API to get metrics from flyspray projects | Unconfirmed | |
| | | 29.03.2015 | 06.10.2015 | |
|
1988 | Installer and Upgrader | Bug Report | Medium | Password Field for Admin | Unconfirmed | |
| | | 02.04.2015 | 12.05.2015 | |
|
1991 | User Interface | Feature Request | Medium | Abillity to drill into progress graph from toplevel vie... | New | |
| | | 17.04.2015 | 24.04.2015 | |
|
1999 | XMPP/Jabber | Feature Request | Medium | jabber xmpp configuration | New | |
| | 1 | 22.06.2015 | 11.02.2017 | |
|
2012 | Backend/Core | Feature Request | Medium | Managing Tags | New | |
| 1.1 devel | | 18.07.2015 | 12.11.2015 | |
|
2016 | User Interface | TODO | Medium | heading and h1, h2, h3 | New | |
| 1.1 devel | | 23.07.2015 | 23.07.2015 | |
|
2019 | User Interface | Feature Request | Medium | title -tag | Waiting on Customer | |
| 1.1 devel | | 26.07.2015 | 26.07.2015 | |
|
2020 | XMPP/Jabber | Feature Request | Medium | Function to test jabber/xmpp configuration | New | |
| 1.1 devel | 1 | 31.07.2015 | 19.09.2015 | |
|
2028 | Text Rendering | Bug Report | Medium | upgrade dokuwiki 'plugin' | New | |
| | | 12.08.2015 | 20.08.2015 | |
|
2040 | Installer and Upgrader | Information | Medium | FS1.0 Release builds | Confirmed | |
| 1.0 | | 23.08.2015 | 17.04.2019 | |
|
2042 | Backend/Core | Bug Report | Medium | function absoluteURI not using basedir and force_basedi... | Unconfirmed | |
| | 1 | 04.09.2015 | 01.10.2015 | |
|
2047 | User Interface | Feature Request | Medium | Inserting images/screenshots from buffer | Unconfirmed | |
| | 1 | 04.09.2015 | 29.09.2015 | |
|
2049 | Backend/Core | Feature Request | Medium | Display login page or customizable page to anonymous us... | Unconfirmed | |
| | | 09.09.2015 | 04.04.2016 | |
|
2065 | User Interface | Feature Request | Medium | One click signup (with facebook, twitter , Google, yaho... | Unconfirmed | |
| | 1 | 09.10.2015 | 03.03.2016 | |
|
2066 | Installer and Upgrader | Feature Request | Medium | Automated site update (like Wordpress) | Unconfirmed | |
| | 2 | 09.10.2015 | 10.10.2015 | |
|
2074 | User Interface | Bug Report | Medium | Opening tasks from tasklist | New | |
| 1.0 | | 18.10.2015 | 18.07.2016 | |
|
2078 | User Interface | Bug Report | Medium | layout of requested close on small displays | New | |
| 1.0 | | 26.10.2015 | 29.10.2015 | |
|
2085 | Text Rendering | Information | Medium | Enabling Color Coding options in CKEDITOR | Unconfirmed | |
| | | 30.10.2015 | 30.10.2015 | |