|
2201 | API | Bug Report | High | I got Fatal Error on the Github OAuth | Unconfirmed | |
| 1.0 | | 07.09.2016 | 09.09.2016 |
Task Description
Fatal error: Class 'League\OAuth2\Client\Provider\Github' not found in /html/bugs/includes/GithubProvider.php on line 11
I have downloaded this: Precompiled with 3rd party libs for PHP5.6: flyspray-1.0-rc1_php56.tgz and the file seems really dont exist.
|
|
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?
|
|
2112 | API | Bug Report | Medium | Assigned tickets aren't editable for lower privileged u... | Unconfirmed | |
| | | 31.03.2016 | 11.04.2016 |
Task Description
An assigned ticket can't be edited by a lower privileged user.
Steps to reproduce:
One Project, Two Users. User A is Admin, User B is Basic
A creates a Task.
A take ownership of the Task. (it’s important to do this AFTER saving the task. You cannot assign User A if you are A in this moment. Maybe another Bug...!?)
Now B is allowed to take ownershop too. B click now “Add me to assignees”.
Now B can edit the task.
If B click “save”, the task can’t be saved, because some fields haven’t the correct values (esp: state is now “unconfirmed”). Many error messages said, that unexpected values exist
Some weird moments:
Why can B edit a task? He have no rights to edit tasks...
If B are Basic and have “edit own Task”-Right too, this bug also exist.
|
|
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.
|
|
2107 | Authentication | Feature Request | Low | Support CAS Server Authenticate | Unconfirmed | |
| | | 02.03.2016 | 04.09.2019 |
Task Description
Please support Central Authentication Service, thank you.
|
|
2209 | Authentication | Feature Request | Medium | TLS support for LDAP | Unconfirmed | |
| | 1 | 09.10.2016 | 04.09.2019 |
Task Description
It would be helpful to have communication with LDAP via TLS
|
|
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.
|
|
2607 | Authentication | Bug Report | Low | Whitespaces in email address field | Unconfirmed | |
| | | 03.05.2020 | 03.05.2020 |
Task Description
When I try to register at flyspray and add a space before the email address, registering does not work, I get the error message: “You did not enter a valid email address”. But my email progam ignores the space when I do the same there.
|
|
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.
|
|
1792 | Backend/Core | Feature Request | Low | Changes from Deprecated 1.0.0 | New | |
| 2.1 | | 13.12.2012 | 03.03.2013 |
Task Description
Someone should go through all the changes from 1.0.0 and figure out which features should be ported to 1.0 devel and open tickets for them, and/or open tickets for the items that should be done in 2.0
|
|
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.
|
|
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.
|
|
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.
|
|
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
|
|
1734 | Backend/Core | Bug Report | Low | Add Timezone Selection to Admin Panel | Maybe | |
| 2.0 | | 12.05.2012 | 07.03.2015 |
Task Description
Add Timezone Selection to Admin Panel
|
|
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
|
|
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.
|
|
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.
|
|
1774 | Backend/Core | Feature Request | Low | Email Layout | Maybe | |
| 2.0 | | 11.10.2012 | 20.07.2015 |
Task Description
Hello, it is possible to change the layout for notification mails? I'll put our logo into Mail body and I'll format the text in different font-styles.
Thank you!
|
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 07.01.2020 |
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.
|
|
1798 | Backend/Core | Feature Request | Low | Bounty System | New | |
| 2.0 | | 13.12.2012 | 06.03.2015 |
Task Description
Add a system where people can donate towards a specific task. For example, I want to donate $10 if someone implements gravatars. The money sits in a pool, and then when someone claims that task and it is marked as completed by the admin, they get the bounty (less some commission that goes towards the project).
|
|
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
|
|
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.
|
|
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
|
|
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
|
|
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 | |
|
1843 | Backend/Core | Feature Request | Low | Attach 1 ticket to multiple projects | Maybe | |
| 2.0 | | 07.03.2013 | 06.03.2015 | |
|
1858 | Backend/Core | Feature Request | Low | Clone Tasks and Projects | Maybe | |
| 2.0 | | 02.04.2013 | 15.09.2017 | |
|
1866 | Backend/Core | Feature Request | Low | API for automatically report a bug | Maybe | |
| 2.0 | 1 | 08.05.2013 | 06.03.2015 | |
|
1868 | Backend/Core | Feature Request | Low | One issue for multiple components | Maybe | |
| 2.0 | | 22.06.2013 | 12.11.2015 | |
|
1871 | Backend/Core | Feature Request | Low | Restricted Task Types Based on Group | Maybe | |
| 2.0 | | 19.07.2013 | 06.03.2015 | |
|
1876 | Backend/Core | Feature Request | Low | Add wiki page tab | Planned | |
| 2.0 | 1 | 26.09.2013 | 06.03.2015 | |
|
2054 | Backend/Core | Feature Request | Low | Fields for csv export choosable like for task list | New | |
| 2.0 | | 17.09.2015 | 31.12.2017 | |
|
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 | |
|
1720 | Backend/Core | Feature Request | Low | Better Access Control Lists and User / Group Management | Planned | |
| 1.1 devel | | 01.05.2012 | 20.03.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 | |
|
1812 | Backend/Core | Feature Request | Low | Multiple email addresses | Planned | |
| 1.1 devel | | 17.01.2013 | 30.12.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 | |
|
1849 | Backend/Core | Feature Request | High | Installer Overhaul | Planned | |
| 1.1 devel | | 15.03.2013 | 15.07.2016 | |
|
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 | |
|
1919 | Backend/Core | Bug Report | Low | AJAX Quick-Edit on category and task pages | Planned | |
| 1.1 devel | 1 | 09.07.2014 | 07.12.2015 | |
|
1924 | Backend/Core | Bug Report | Low | Better errors messages on email error | New | |
| 1.1 devel | | 11.07.2014 | 06.03.2015 | |
|
1955 | Backend/Core | TODO | Low | Codestyle | Confirmed | |
| 1.1 devel | | 07.03.2015 | 09.03.2015 | |
|
1956 | Backend/Core | TODO | Low | Dates | Confirmed | |
| 1.1 devel | | 07.03.2015 | 09.03.2015 | |
|
1973 | Backend/Core | TODO | Low | url rewrite | Planned | |
| 1.1 devel | | 14.03.2015 | 11.02.2016 | |
|
1975 | Backend/Core | Feature Request | Low | Batch processing of tasks in tasklist | Planned | |
| 1.1 devel | 1 | 15.03.2015 | 13.12.2016 | |
|
1976 | Backend/Core | Feature Request | Low | Save sorting for actual project | Planned | |
| 1.1 devel | | 15.03.2015 | 15.03.2015 | |