|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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 |
Task Description
When some url to a bug is redirected to the login page, because the user does not have the right to see the bug without login, the user should be redirected after the login to the url he wanted to see.
Maybe redirect to /login/?next=/task/X and put the next-url in a hidden field in the login-form, so flyspray can redirect to the correct page after login. Even preserving anchor-urls (#comment-YYYY) would be cool, but i guess this needs Javascript to work.
|
|
1955 | Backend/Core | TODO | Low | Codestyle | Confirmed | |
| 1.1 devel | | 07.03.2015 | 09.03.2015 |
Task Description
So, the new website is now online, the codestyle part is empty and I think we need to speak about them...
I can happily reformat the whole project once we have decided the whole thing. Don't forget, too strict code style leads to code style not being respected, so crap like max line length should be avoided. I personnaly don't know anybody coding from their mobile phones. I sometimes do check some code on it, but long lines never disturbed me as long as the line is not 5k chars long.
I think we should go for a standard one.
Things like:
- Do use brackets even if single lined condition - Variable names have spaces replaced by the next words first letter in capital, start with a lower case - Same goes for functions - Etc etc. Pretty much of PSR-1 maybe 2
What I don't understand is the use of spaces, and I'd be for tabs instead of 4 spaces (some files use 2 spaces, some 3...). Most of the dev tools are by default set to use tabs and not spaces. And be seeing the code now we see that it clearly. So i'd be for reformatting into tabs, the whole, and same time fixing the broken identation in every files.
I could write it down for the website
|
|
1956 | Backend/Core | TODO | Low | Dates | Confirmed | |
| 1.1 devel | | 07.03.2015 | 09.03.2015 |
Task Description
Upon my implementation for an easier date selector, I think we should rework it as follow:
|
|
1981 | Backend/Core | TODO | Low | Unify event logging and notifications | Confirmed | |
| 1.1 devel | | 20.03.2015 | 22.03.2015 |
Task Description
They are currently two separate mechanisms. Shouldn't be so. Events happen always, notifications when someone should be or have chosen to be notified about those events.
Besides, the current code is just a total mess that should be fixed/rewritten anyway, and we unfortunately also overlooked during the development phase 2 things: one new table, users_emails, and the fact that the user is now allowed to give several email addresses separated by a semicolon.
|
|
2101 | Backend/Core | Bug Report | Low | Mobile view GUI bug | Confirmed | |
| | | 18.02.2016 | 24.02.2016 |
Task Description
As you can see on screenshot attachment the GUI on mobile view is not OK.
I marked with red field what need to be fixed.
Phone used: Samsung Note 4.
|
|
2121 | Backend/Core | Bug Report | Medium | 'my assigned tasks' uses like %?% search instead of use... | Confirmed | |
| 1.0 | | 19.04.2016 | 03.02.2018 |
Task Description
Problem: https://github.com/Flyspray/flyspray/pull/552
The button ‘My assigned tasks’ should search only by userid, not in username or realname with the LIKE ‘%...%’ operator.
Currently the button is using the same as doing an advanced search filling the ‘Assigned To’ input field. (currently ‘dev’ param) But that search param searches in userid, username and realname.
Edit: Implemented simpler solution: if param is digitsonly, then search by userid, otherwise by username and realname if that param exists.
|
|
2135 | Backend/Core | Bug Report | High | "Modify own tasks" does not function correctly when add... | Confirmed | |
| 1.0 | 1 | 07.06.2016 | 22.08.2016 |
Task Description
“Oh, there are some incompatible properties set that must be resolved before moving this task to a different project.”
Oh, but I am not moving the task to a different project. Just trying to edit my own submission.
“Edit this task” → “Save details”
See attached screen capture.
|
|
2207 | Backend/Core | Bug Report | High | Nonpublic project titles and project description exposi... | Confirmed | |
| 1.0 | | 23.09.2016 | 29.09.2016 |
Task Description
When a anonymous user tries to display a ticket of a non public project (for example by entering a random ticket id), Flyspray exposes the title of the non public project in the header bar.
Edit by peterdd: also applies to project description
|
|
2451 | Backend/Core | Feature Request | Low | Mod: blank Category - user must chose before pressing A... | Confirmed | |
| | | 08.12.2017 | 14.12.2017 |
Task Description
Hello Peter,
I am interested in making the following mod:
When posting a new task, category should be blank by default, in order for the user that opens a new task to select that specific category. If he doesn’t select any task, when pressing Add this task button, FlySpray should display an error message saying that the Category hasn’t been specified.
Do you think this mod can be made with the current version? If so, do you mind if you help me a bit with the things that need to be modified?
Thanks!
|
|
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
|
|
2616 | Backend/Core | Bug Report | Medium | There is a problem after a http/https link on a line wi... | Confirmed | |
| | | 25.09.2020 | 10.11.2020 |
Task Description
When we add http/https links there is a problem.
I think, the problem is here for other URI too.
Examples:
1/ With this code without code section : The code:
blablabla
- https://example.tld
- https://example.tld
We obtain:
The code : blablabla - https://example.tld - https://example.tld
2/ Same to with a text in more, with this code without code section : The code:
blablabla
- example 1 https://example.tld/
- example 2 https://example.tld/
We obtain:
The code : blablabla - example 1 https://example.tld/ - example 2 https://example.tld/
|
|
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.
|
|
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 | |
|
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 | |
|
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 | |
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 | |
|
2096 | Backend/Core | Feature Request | Very Low | Add an option to force https | Maybe | |
| | | 16.01.2016 | 17.01.2016 | |
|
2617 | Backend/Core | Feature Request | Low | Preview button not at the good place | Maybe | |
| | | 26.09.2020 | 26.09.2020 | |
|
1237 | Backend/Core | Feature Request | Medium | Allow Multiple Owners Per Category | Planned | |
| 2.0 | 7 | 09.04.2007 | 10.08.2015 | |
|
1720 | Backend/Core | Feature Request | Low | Better Access Control Lists and User / Group Management | Planned | |
| 1.1 devel | | 01.05.2012 | 20.03.2015 | |
|
1766 | Backend/Core | Feature Request | Low | Allow users to choose their favourite theme | Planned | |
| 2.0 | 1 | 16.08.2012 | 04.08.2015 | |
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 07.01.2020 | |
|
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 | |
|
1823 | Backend/Core | Feature Request | Low | Comments with edit changes | Planned | |
| 2.0 | | 30.01.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 | |
|
1849 | Backend/Core | Feature Request | High | Installer Overhaul | Planned | |
| 1.1 devel | | 15.03.2013 | 15.07.2016 | |
|
1876 | Backend/Core | Feature Request | Low | Add wiki page tab | Planned | |
| 2.0 | 1 | 26.09.2013 | 06.03.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 | |
|
1973 | Backend/Core | TODO | Low | url rewrite | Planned | |
| 1.1 devel | | 14.03.2015 | 11.02.2016 | |