|
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.
|
|
920 | User Interface | Feature Request | Low | Charts (gantt, severities, OSes, opened-closed, ...) | Researching | |
| 2.0 | 8 | 06.05.2006 | 18.07.2015 |
Task Description
With all informations on flyspray, it's possible to generate a gantt chart.
For this, some php code exists :
- http://www.aditus.nu/jpgraph/
- http://www.graphviz.org/
- http://www.phpclasses.org/browse/package/2737.html
|
|
1040 | User Interface | Feature Request | Low | Close Multiple Tasks at once | New | |
| 1.1 devel | 3 | 17.08.2006 | 01.10.2015 |
Task Description
We don't close the tasks until the release is "made", that is we let them under "Requires Testing" with 100% complete. When the release/testing cycle is finished, somebody has to go task by task, and start closing them... it's a PITA ;) It would be nice to have to option to select all the tasks you want to close, and that the "popup" when you enter the reason/etc, applied to all the tasks I selected...
I recall reading something about this in the past, but haven't found it; and if this is implemented, I haven't seen a way to do it in 099beta1
|
|
1134 | User Interface | Feature Request | Low | add icon/image for each project | Planned | |
| 1.1 devel | 3 | 29.11.2006 | 09.03.2015 |
Task Description
When we have several projects into flyspray, it's hard to see the project where I am when I add several tasks. It's necessary to read the text.
To improve this, I think that it's a good idea if it's possible to add a color or an image with the logo project next to project title into web page. It will more simple to know where we are when we use flyspray.
|
|
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.
|
|
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.
|
|
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.
|
|
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
|
|
1485 | User Interface | Feature Request | Low | Additional extended Printview for the Tasks | Planned | |
| 2.0 | | 13.05.2008 | 11.03.2015 |
Task Description
It would be useful to print a list of tasks in a extended version. e.g. All tasks from a programmer with all the details of it.
|
|
1487 | Authentication | Feature Request | Low | LDAP(Active Directory) Authentication | Planned | |
| 1.1 devel | 11 | 21.05.2008 | 04.09.2019 |
Task Description
I have done a very quick bit of work to bring ldap (through active directory) authentication to flyspray for our implementation in the office. I hope it will be of use to others. There is a readme.txt inside talking through the process and the patch to apply. My plan is to expand on this and make it part of the setup process but this will take a bit longer.
|
|
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?
|
|
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
|
|
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.
|
|
1529 | Backend/Core | Bug Report | Low | Inactivity-close doesn't work, bug is left open | Maybe | |
| 2.0 | | 07.01.2009 | 24.09.2015 |
Task Description
If you define an inactivity-close value in hours/days (haven't tried weeks) the bug is still open when the time expires.
|
|
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.
|
|
1599 | User Interface | Feature Request | Low | Implement "Tasks not blocked by other tasks" | Unconfirmed | |
| 2.1 | 1 | 11.08.2009 | 03.03.2013 |
Task Description
In the advanced search, there is "Tasks not blocking other tasks"
Implement a related: "Unblocked tasks" (i.e. Tasks not blocked by other tasks)
|
|
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.
|
|
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.
|
|
1673 | Backend/Core | Bug Report | High | Only white screen after upgrade to 1.0 - reasons | Confirmed | |
| 1.1 devel | 4 | 12.01.2011 | 17.08.2016 |
Task Description
After I upgraded to version 1.0 (the upgrade was successful), flyspray only shows a white page (and the source in firefox shows, that the page is completely white).
Please help us finding the roots of these bugs!
We think most cases of that “white screen” are relying on the third party vendor libraries behavior we use. When a library detects an error, sometimes they just call die() or exit; of php, but suppress error messages. So the script just stopped not giving any output to browser.
The dev versions from github use composer for installing the required libraries. We will package them on the final release together and make sure most cases of “white screen” are fixed.
|
|
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
|
|
1720 | Backend/Core | Feature Request | Low | Better Access Control Lists and User / Group Management | Planned | |
| 1.1 devel | | 01.05.2012 | 20.03.2015 |
Task Description
We need to have a better way to do user rights, group rights and manage users.
Here is what I am thinking, global administration can go to a ACL tab. Click on it and you have a simple way to add a new user / group. Two tabs on top are User Rights and Group Rights. These are global so each project will inherit the global setting for user / group.
Clicking on User Rights tab will lists users with a table to grant user rights. Specific to that user, it would be the same for group rights tab.
You can also search by a user name. This will make things faster to find that specific user.
|
|
1734 | Backend/Core | Bug Report | Low | Add Timezone Selection to Admin Panel | Maybe | |
| 2.0 | | 12.05.2012 | 07.03.2015 | |
|
1736 | User Interface | Feature Request | Low | Be able to add colors for Task Statuses | Planned | |
| 1.1 devel | | 16.05.2012 | 15.10.2015 | |
|
1737 | Javascript | TODO | Low | Javascript Overhaul | New | |
| 1.1 devel | 1 | 25.05.2012 | 24.02.2016 | |
|
1748 | Database Queries | Feature Request | Low | Sort by recent activity | Planned | |
| 1.1 devel | | 17.06.2012 | 11.03.2015 | |
|
1749 | User Interface | Bug Report | Low | Submit form buttons on lower right | Unconfirmed | |
| | | 17.06.2012 | 24.09.2015 | |
|
1751 | Backend/Core | Feature Request | Medium | Default to show all in Event Log | Confirmed | |
| 1.1 devel | 1 | 20.06.2012 | 09.02.2016 | |
|
1753 | Backend/Core | Feature Request | Medium | Usergroup Restriction: Only View Summary | Confirmed | |
| 1.1 devel | 2 | 20.06.2012 | 27.06.2016 | |
|
1760 | Backend/Core | Feature Request | Low | Column 'last commenter' in tasks list view | Maybe | |
| 2.0 | 2 | 27.07.2012 | 25.10.2016 | |
|
1766 | Backend/Core | Feature Request | Low | Allow users to choose their favourite theme | Planned | |
| 2.0 | 1 | 16.08.2012 | 04.08.2015 | |
|
1772 | Backend/Core | Feature Request | Low | Different kinds of votes | Maybe | |
| 2.0 | 1 | 23.09.2012 | 09.03.2015 | |
|
1774 | Backend/Core | Feature Request | Low | Email Layout | Maybe | |
| 2.0 | | 11.10.2012 | 20.07.2015 | |
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 07.01.2020 | |
|
1783 | Notifications | Feature Request | Medium | Create account for non-logged user automatically | Planned | |
| 2.0 | | 27.11.2012 | 07.03.2015 | |
|
1791 | Backend/Core | Feature Request | Medium | Ability to merge version, OS, etc | Suspended | |
| | 1 | 12.12.2012 | 12.01.2017 | |
|
1792 | Backend/Core | Feature Request | Low | Changes from Deprecated 1.0.0 | New | |
| 2.1 | | 13.12.2012 | 03.03.2013 | |
|
1798 | Backend/Core | Feature Request | Low | Bounty System | New | |
| 2.0 | | 13.12.2012 | 06.03.2015 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.2015 | |
|
1811 | Backend/Core | Feature Request | Low | Google Docs/Dropbox Integration | New | |
| 2.0 | | 17.01.2013 | 13.03.2015 | |
|
1812 | Backend/Core | Feature Request | Low | Multiple email addresses | Planned | |
| 1.1 devel | | 17.01.2013 | 30.12.2015 | |
|
1818 | Backend/Core | Feature Request | Low | Git/SVN/CVS Integration | Planned | |
| 2.0 | 2 | 17.01.2013 | 12.08.2015 | |
|
1819 | Backend/Core | Feature Request | Low | Communicate via email | Planned | |
| 2.0 | 3 | 17.01.2013 | 18.10.2016 | |
|
1820 | Backend/Core | Feature Request | Low | Merge comments, history, and details | New | |
| 2.0 | | 17.01.2013 | 25.05.2016 | |
|
1823 | Backend/Core | Feature Request | Low | Comments with edit changes | Planned | |
| 2.0 | | 30.01.2013 | 06.03.2015 | |
|
1834 | Backend/Core | Feature Request | Low | user profile page | Maybe | |
| 2.0 | | 25.02.2013 | 06.03.2015 | |
|
1836 | Backend/Core | Feature Request | Low | Need permission option to view only own tasks | Planned | |
| 1.1 devel | | 27.02.2013 | 22.04.2015 | |