|
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.
|
|
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.
|
|
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
|
|
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.
|
|
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
|
|
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.
|
|
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
|
|
1999 | XMPP/Jabber | Feature Request | Medium | jabber xmpp configuration | New | |
| | 1 | 22.06.2015 | 11.02.2017 |
Task Description
There should be some help at the configuration sections for setting up jabber/xmpp notifications.
How someone can test it?
Must the admin setup his own jabber/xmpp server or are there recommended servers?
I registered with psi+ instant messager as peterdd@ubuntu-jabber.de at ubuntu-jabber.de for testing and configured it here in my account too, but got no jabber messages.
Email notifications works and I set up both sending.
|
|
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.
|
|
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.
|
|
1748 | Database Queries | Feature Request | Low | Sort by recent activity | Planned | |
| 1.1 devel | | 17.06.2012 | 11.03.2015 |
Task Description
It would be great to sort the task list by recent activity. This would mean any change to an issue, including new comments, would rise to the top. This would make it easy to keep up on recent discussion even if you don't want to get every single detail via notifications.
|
|
1836 | Backend/Core | Feature Request | Low | Need permission option to view only own tasks | Planned | |
| 1.1 devel | | 27.02.2013 | 22.04.2015 |
Task Description
In global permissions there is 'View tasks'. This makes it so a user can view all tasks. Need a way instead that they can view only their own tasks, for example a permission called 'View own tasks'.
If 'View own tasks' is checked for a user, in the project list we should only show projects which contain tickets that that user is a part of. Within a given project we should then only show tickets that the user is a part of if they have that permission set.
So for example if 'View tasks' is set, show user all tasks. 'View tasks' is not set, but 'View own tasks' is set then show them only their own tasks and projects.
|
|
2322 | User Interface | Feature Request | Medium | Mention System | New | |
| | 1 | 07.12.2016 | 19.10.2019 |
Task Description
Hello together,
it would be nice, if you could mention user in your ticket or comment which are not following the task. for example when i will type @nickname, the user “nickname” should be get a e-mail that he is mentioned in the ticket.
(if we are “fancy” then we can print a automcomplete after the @-sign ist typed)
|
|
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
|
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 |
Task Description
Currently projects in Flyspray are active or set inactive.
It will be great to archive project if finished or abandoned. In this case it will not be shown in project overview page and project navigation combo.
|
|
2303 | User Interface | Feature Request | Very Low | Home screen for private flysprays | Requires testing | |
| | | 25.10.2016 | 26.10.2016 |
Task Description
I use Flyspray as a closed system with all projects set to private. I use it as a main means of communication with my clients. In such a case it would be a good idea for visitors to see a home screen (preferably a blank/splash screen with login option only) and definitely not the All tasks title or project names ( FS#2302 ) or taskid search.
|
|
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
|
|
1736 | User Interface | Feature Request | Low | Be able to add colors for Task Statuses | Planned | |
| 1.1 devel | | 16.05.2012 | 15.10.2015 |
Task Description
I often used color identifiers for my Task Statuses in my old bug tracking solution, and it helped me prioritize things, like confirming unconfirmed bugs. The only thing that currently has colors, is the severity- I’d like a possibility to have (customizable) colors for Task Statuses too.
|
|
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.
|
|
1849 | Backend/Core | Feature Request | High | Installer Overhaul | Planned | |
| 1.1 devel | | 15.03.2013 | 15.07.2016 |
Task Description
The application installer needs an overhaul, all strict notices fixed and the associated dependant tasks resolved.
|
|
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
|
|
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.
|
|
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.
|
|
1811 | Backend/Core | Feature Request | Low | Google Docs/Dropbox Integration | New | |
| 2.0 | | 17.01.2013 | 13.03.2015 | |
|
1972 | User Interface | Feature Request | Low | Advanced search form - ideas for faster/better usabilit... | New | |
| 1.1 devel | | 12.03.2015 | 18.03.2019 | |
|
2012 | Backend/Core | Feature Request | Medium | Managing Tags | New | |
| 1.1 devel | | 18.07.2015 | 12.11.2015 | |
|
2522 | Backend/Core | Feature Request | Low | email vs username login issues | Researching | |
| | | 31.10.2018 | 02.11.2018 | |
|
2566 | Installer and Upgrader | Feature Request | Medium | syntax_plugin after an upgrade from 0.9.9.7 -> 1.0-rc9 | Unconfirmed | |
| | 1 | 30.08.2019 | 14.09.2019 | |
|
1236 | User Interface | Feature Request | Low | Mark Issue As Verified or Unverifiable | Unconfirmed | |
| | 4 | 09.04.2007 | 18.07.2016 | |
|
1720 | Backend/Core | Feature Request | Low | Better Access Control Lists and User / Group Management | Planned | |
| 1.1 devel | | 01.05.2012 | 20.03.2015 | |
|
1812 | Backend/Core | Feature Request | Low | Multiple email addresses | Planned | |
| 1.1 devel | | 17.01.2013 | 30.12.2015 | |
|
1820 | Backend/Core | Feature Request | Low | Merge comments, history, and details | New | |
| 2.0 | | 17.01.2013 | 25.05.2016 | |
|
1847 | User Interface | Feature Request | Low | Make default theme responsive | Planned | |
| 1.1 devel | | 14.03.2013 | 16.10.2015 | |
|
1876 | Backend/Core | Feature Request | Low | Add wiki page tab | Planned | |
| 2.0 | 1 | 26.09.2013 | 06.03.2015 | |
|
1969 | User Interface | Feature Request | Low | search form with Advanced search toggle layout | New | |
| 1.1 devel | | 12.03.2015 | 19.09.2015 | |
|
1975 | Backend/Core | Feature Request | Low | Batch processing of tasks in tasklist | Planned | |
| 1.1 devel | 1 | 15.03.2015 | 13.12.2016 | |
|
2096 | Backend/Core | Feature Request | Very Low | Add an option to force https | Maybe | |
| | | 16.01.2016 | 17.01.2016 | |
|
2108 | User Interface | Feature Request | Medium | Support local language when install Flyspray | Confirmed | |
| | 1 | 03.03.2016 | 15.07.2016 | |
|
2325 | User Interface | Feature Request | Low | big image attachments: fit to browser window width in L... | New | |
| | | 10.01.2017 | 11.01.2017 | |
|
2327 | Backend/Core | Feature Request | Low | visibility-option for private tasks | Unconfirmed | |
| | | 15.01.2017 | 17.01.2017 | |
|
2520 | Notifications | Feature Request | Low | Send a notification for a new task in slack integration... | Unconfirmed | |
| | | 24.10.2018 | 19.03.2019 | |
|
1539 | Backend/Core | Feature Request | Low | Sitemap.xml Generation | Unconfirmed | |
| 2.1 | 1 | 12.01.2009 | 11.03.2015 | |
|
1612 | Backend/Core | Feature Request | Low | Allow Comments by anonymous Users | Unconfirmed | |
| 2.0 | 1 | 20.10.2009 | 17.01.2013 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.2015 | |
|
1823 | Backend/Core | Feature Request | Low | Comments with edit changes | Planned | |
| 2.0 | | 30.01.2013 | 06.03.2015 | |
|
1868 | Backend/Core | Feature Request | Low | One issue for multiple components | Maybe | |
| 2.0 | | 22.06.2013 | 12.11.2015 | |
|
1957 | User Interface | Feature Request | Low | automatic temporary storing while writing/editing task | Researching | |
| | | 09.03.2015 | 12.03.2015 | |
|
1962 | Backend/Core | Feature Request | Low | SMS notification - sending notifications via sms same a... | New | |
| | | 11.03.2015 | 02.12.2015 | |