|
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
|
|
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.
|
|
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?
|
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 28.04.2016 |
Task Description
A very useful feature would be to be able to manage a list of custom fields by project, and to be able to add and fill any of these fields to any task. So we could be able to search on the presence and content of a field. We could be able to sort the tasks by this field when they are displayed in a list.
A use example is when you create a bug by reference to another external list. It can be very useful to have a field that references a line in the external list.
|
|
1819 | Backend/Core | Feature Request | Low | Communicate via email | Planned | |
| 2.0 | 3 | 17.01.2013 | 18.10.2016 |
Task Description
Need to be able to email back and forth to communicate with flyspray. Ideally flyspray can be CC'ed on an email or can replay to a notification which would add the body and/or attachments to the thread. This goes back to reworking the way people interact with and view tickets
|
|
1818 | Backend/Core | Feature Request | Low | Git/SVN/CVS Integration | Planned | |
| 2.0 | 2 | 17.01.2013 | 12.08.2015 |
Task Description
Should be able to reference a ticket # when committing code, and then have a way to input your repository path to flyspray, and let it search all your commits for ticket #'s. Then should parse it, and have a link to that commit within the ticket.
|
|
1760 | Backend/Core | Feature Request | Low | Column 'last commenter' in tasks list view | Maybe | |
| 2.0 | 2 | 27.07.2012 | 25.10.2016 |
Task Description
Hey Flyspray Team,
a nice feature would be to see which user commented recently on a task. This could be a simple new column in the tasks list view.
Regards,
hoc
|
|
1772 | Backend/Core | Feature Request | Low | Different kinds of votes | Maybe | |
| 2.0 | 1 | 23.09.2012 | 09.03.2015 |
Task Description
It would be nice to have multiple kinds of votes, e.g. yes/no.
|
|
1866 | Backend/Core | Feature Request | Low | API for automatically report a bug | Maybe | |
| 2.0 | 1 | 08.05.2013 | 06.03.2015 |
Task Description
Actually you can't automatically add a bug report. Or i haven't found it. In a first time a simple report via email or webservice could be great.
- Project Name - Message - System - Version - Status –> New - Priority → Normal - Category –> On a new category (created by default) : 'Automated report bug'
Sorry for bad grammar, i'am not english.
|
|
1766 | Backend/Core | Feature Request | Low | Allow users to choose their favourite theme | Planned | |
| 2.0 | 1 | 16.08.2012 | 04.08.2015 |
Task Description
add a theme Setting in the user details, where the user can override the global theme setting (maybe even per project?) with his favourite theme.
|
|
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
|
|
1876 | Backend/Core | Feature Request | Low | Add wiki page tab | Planned | |
| 2.0 | 1 | 26.09.2013 | 06.03.2015 |
Task Description
It will quite useful to have wiki page for project.
|
|
1834 | Backend/Core | Feature Request | Low | user profile page | Maybe | |
| 2.0 | | 25.02.2013 | 06.03.2015 |
Task Description
Should have a page that is a users profile page. so clicking in that users name on a ticket takes you there and you can see what bugs are assigned to them, what they have commented on, and other info about them and about their activity.
|
|
1980 | User Interface | Feature Request | Medium | Tasklist - PDF Export | Maybe | |
| 2.0 | | 19.03.2015 | 26.05.2016 |
Task Description
Hello,
First of all, thanks for this great tool. Can you please add also PDF export for Tasklist?
Thank You.
|
|
1871 | Backend/Core | Feature Request | Low | Restricted Task Types Based on Group | Maybe | |
| 2.0 | | 19.07.2013 | 06.03.2015 |
Task Description
I have a public bug tracker and would like to have a TODO like task, except restricted so only the developers can set the task type to TODO, while the general reporters can just submit bug reports or feature requests.
|
|
2013 | User Interface | Feature Request | Low | personal task list column selection and positioning | New | |
| 2.0 | | 20.07.2015 | 06.10.2015 |
Task Description
Currently the appearence of the task list table is configured system wide for all project view and project wide for project task list views.
Even more fancy and for power users would be if the user can set his own project column list view preferences for projects.
While the project columns for the task list are configured by "visible_columns" we could use the project wide "visible_fields" as allowed columns the user may configure as his personal preference. If the user doesn't configure his own list, the project default list is used. The user should have the option to reset to project default. (e.g. empty personal "visible_fields" )
In this case the description for setting "visible_fields" on the project management configuration page must be adapted too.
Probably a new table required something like:
CREATE TABLE {user_projects} (
user_id int,
project_id,
columns varchar(255) DEFAULT '',
);
or
CREATE TABLE {user_projects} (
user_id int,
project_id,
columns varchar(32) DEFAULT NULL,
sort int,
);
|
|
1868 | Backend/Core | Feature Request | Low | One issue for multiple components | Maybe | |
| 2.0 | | 22.06.2013 | 12.11.2015 |
Task Description
Hi,I would like to see a enhancement, where you can submit/edit and assign it to multiple components, as it needs work from multiple sides.
For example: A user asks for a new object to be visualized. This includes work of the GUI designers and altering internal core structures. For internal management, I would like to label this for both teams.
|
|
1820 | Backend/Core | Feature Request | Low | Merge comments, history, and details | New | |
| 2.0 | | 17.01.2013 | 25.05.2016 |
Task Description
Should be more of a link thread of activity rather than segmented
|
|
1857 | User Interface | Feature Request | Low | Login and then submit new task | Researching | |
| 2.0 | | 27.03.2013 | 06.03.2015 |
Task Description
Hello, when I wanted to use Flyspray to manage request from non-technical customer, I found one missing feature:
I have "report a problem" link on devel version of web site. But to submit new task, it is necessary to login into Flyspray.
It would be nice if there was an URL with login form if user is not logged in and "add new task" form if he is logged in.
Example scenario: - Customer visits devel site after some time and finds some problem. He wants to report it. - Customer clicks "report a problem" on the devel site and Flyspray is opened. - Customer now see some wierd error message and has no idea what is wrong. If anonymous reports are allowed, he sees the form, but cannot upload screenshots and he must enter his e-mail address.
How it should be: - Customer visits devel site after some time and finds some problem. He wants to report it. - Customer clicks "report a problem" on the devel site and Flyspray is opened. - Customer sees login form and (if anonymous reports are allowed) there is also "add new task" form below the login form. - Customer clicks "login" (password is saved in browser). - Customer now can fill report with all the comfort.
|
|
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.
|
|
1811 | Backend/Core | Feature Request | Low | Google Docs/Dropbox Integration | New | |
| 2.0 | | 17.01.2013 | 13.03.2015 |
Task Description
On a project or ticket basis should be able to hook in and possibly also share permissions
|
|
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.
|
|
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.
|
|
1882 | Email | Bug Report | Medium | Error with email notification | Planned | |
| 2.0 | | 22.12.2013 | 08.04.2016 |
Task Description
Hello,
First of all, thanks for this great tool, very user friendly. I'm informing you as requested ("This should never happend, please inform Flyspray Developers" :)) because I'm getting this error message:
[Completely unexpected exception: Connection could not be established with host http://ssl0.ovh.net/ [php_network_getaddresses: getaddrinfo failed: Name or service not known #0] This should never happend, please inform Flyspray Developers]
I set up the SMTP configuration (SSL) with information provided.
Enclosed in PHPinfo configuration, if it helps.
Thanks
|
|
1774 | Backend/Core | Feature Request | Low | Email Layout | Maybe | |
| 2.0 | | 11.10.2012 | 20.07.2015 | |
|
2010 | User Interface | Feature Request | Low | effort tracking widget | New | |
| 2.0 | | 18.07.2015 | 18.07.2015 | |
|
2009 | User Interface | Feature Request | Low | Edit task flow | New | |
| 2.0 | | 18.07.2015 | 07.08.2016 | |
|
1783 | Notifications | Feature Request | Medium | Create account for non-logged user automatically | Planned | |
| 2.0 | | 27.11.2012 | 07.03.2015 | |
|
1823 | Backend/Core | Feature Request | Low | Comments with edit changes | Planned | |
| 2.0 | | 30.01.2013 | 06.03.2015 | |
|
1858 | Backend/Core | Feature Request | Low | Clone Tasks and Projects | Maybe | |
| 2.0 | | 02.04.2013 | 15.09.2017 | |
|
1798 | Backend/Core | Feature Request | Low | Bounty System | New | |
| 2.0 | | 13.12.2012 | 06.03.2015 | |
|
1843 | Backend/Core | Feature Request | Low | Attach 1 ticket to multiple projects | Maybe | |
| 2.0 | | 07.03.2013 | 06.03.2015 | |
|
1485 | User Interface | Feature Request | Low | Additional extended Printview for the Tasks | Planned | |
| 2.0 | | 13.05.2008 | 11.03.2015 | |
|
1734 | Backend/Core | Bug Report | Low | Add Timezone Selection to Admin Panel | Maybe | |
| 2.0 | | 12.05.2012 | 07.03.2015 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.2015 | |