|
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.
|
|
1950 | User Interface | TODO | Medium | Solve confusing Flyspray group settings vs Project grou... | Confirmed | |
| 1.0 | | 07.03.2015 | 11.11.2015 |
Task Description
This is taken from FS#1753:
The second reason being there is no way that I know of to automatically set a project usergroup to new members. I only have 1 project, but it seems the Global groups aren’t working (can still see tasks if “View Tasks” is unchecked) and I don’t know how to fix that.
And what I have to say - it is hard to tell if you are on the Flyspray admin settings area or on the admin settings of a project.
Cheapest way is adding some CSS to distinguish this for the user.
But there is in fact more to do to make it user friendly.
TODO: list configurations for project(task types, categories, ..) in Manage Project should also show the system wide list values as hint to avoid duplication.
TODO: project user groups overview should show system wide user group infos as info for project managers to avoid unnecessary complicated configuration settings.
TODO: visualize related permissions that can overrule eachother like ‘view_task’ overrules ‘view_own_tasks’ to avoid misconfigurations
|
|
1978 | User Interface | Bug Report | Low | Compensate degraded usability due added token system an... | Confirmed | |
| 1.0 | | 16.03.2015 | 12.10.2015 |
Task Description
Due to the needed implementation of an anti csrf system into Flyspray 1.0, this are a side effect issues we need to address:
Due the required replacement of action links to form buttons:
Javascriptless CSS3-toggles:
Some clickable labels don’t show pointer icon when :hover. CSS issue, easy fix.
|
|
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.
|
|
2528 | User Interface | Bug Report | Low | New user registration doesn't check for duplicate usern... | Confirmed | |
| | | 05.01.2019 | 07.01.2019 |
Task Description
Steps done to create the problem: Visit https://bugs.flyspray.org/index.php?do=register in a private browser window (so you are logged out)
Put in an already taken username (e.g. Stefan or Stefan2)
Expected behavior: Username gets red and a note appears that username already is taken
Experienced behavior: Username gets green and registration of a new user proceeds with sending a notification mail with confirmation code. After putting in the confirmation code in provided page, user gets presented a “username is already taken, choose another” (where?) message, and has to re-start registration process from beginning and hopefully this time choose a not taken name.
|
|
2425 | Slovenian | Feature Request | Very Low | Translation: Slovenian | Confirmed | |
| | | 05.03.2017 | 05.03.2017 |
Task Description
I prepared Slovenian translation. File is in attachment. You can freely add to release.
|
|
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.
|
|
2108 | User Interface | Feature Request | Medium | Support local language when install Flyspray | Confirmed | |
| | 1 | 03.03.2016 | 15.07.2016 |
Task Description
Please show install page as local language, Thank you.
|
|
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!).
|
|
2040 | Installer and Upgrader | Information | Medium | FS1.0 Release builds | Confirmed | |
| 1.0 | | 23.08.2015 | 17.04.2019 |
Task Description
The Flyspray 1.0alpha1 .zip file release unzips directly to the current directory.
.zip files from github unzip to it’s own directory (flyspray-master.zip unzips to flyspray-master/ ). This is a bit safer, because you cannot accidently mess your directory structure with it.
The release should contain the binary fontawesome files instead of linking to the external CDN. Removes one dependency/singlepointoffailure. How this can be configured for automation? included in Flyspray source now. 
document how a release is exactly created. (consistency, reliability, automation, knowledge sharing for maintainers see below  )
Get in contact with os distributions, that could add Flyspray releases to their repositories (*BSD, Linux distributions, ..) This repositories could add the dependencies like ADODB within the packages (.rpm, .deb,..)
Steps how to do a Flyspray release (since Flyspray 1.0 RC)
Edit includes/class.flyspray.php on github.com and set the correct version for the release there (remove the ' dev’ from the version string), commit as new branch e.g. 1.0-rc1
-
“Release” the Flyspray source on github when satisfied with layout
Run buildscripts for different php versions (see comments at FS#2040)
-
-
Test the created blobs on different servers too.
-
-
-
Send an email to the Flyspray mailing list
-
Maybe we can use this sequence as template on bugs.flyspray.org for releases?
|
|
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.
|
|
2128 | Text Rendering | Bug Report | Low | Geshi (part of dokuwiki plugin for code blocks) uses de... | Confirmed | |
| | 1 | 20.05.2016 | 05.05.2019 |
Task Description
The dokuwiki plugin uses a very old version of geshi for syntax highlighting which uses the deprecated /e modifier in preg_replace in two places rather than preg_replace_callback.
This can trigger warnings such as the following when initially parsing content which uses dokuwiki syntax and includes code:
PHP message: PHP Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/phpapps/flyspray/plugins/dokuwiki/inc/geshi.php on line 2058
PHP message: PHP Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/phpapps/flyspray/plugins/dokuwiki/inc/geshi.php on line 2067
This affects bugs.flyspray.org as well. Several hits came up on google when I search for the following due to the warnings having been displayed ahead of the page content (seen screenshot): flyspray preg_replace_callback
Because flyspray caches the results of processing dokuwiki content then the warnings don’t get emitted if the content has already been cached (so you may find that when you access the url in the screenshot that it doesn’t show the warnings unless you clear the cache entry for that task). Previews can get the warnings spat out as well if there are tagged code sections in the content.
I had a look at a more recent version of geshi (1.0.8.11 from sourceforge) and they had fixed that issue in it (presumably along with a lot of other stuff) so I tried replacing plugins/dokuwiki/inc/geshi.php and plugins/dokuwiki/inc/geshi/* with the 1.0.8.11 versions and that stopped the warnings. I haven’t extensively tested it, but it was processing stuff in code blocks correctly still on the couple of samples I tried.
I guess it’s a separate issue but the new flyspray theme doesn’t have any css styles to apply to the syntax highlighting (if you look at FS#1107 you can see that, and in fact you can see it with the css bit below - if you inspect them with a browser dom inspector you can see that the genshi plugin has parsed and tagged the bits, but no styles are applied so its all just in the default colour). I can raise that as a separate task if worth doing? The following section in bluey stylesheet covered it I think:
.code .br0 {color:#6c6;}
.code .es0 {color:#009;font-weight:700;}
.code .kw1 {color:#b1b100;}
.code .kw2 {color:#000;font-weight:700;}
.code .kw3 {color:#006;}
.code .kw4 {color:#933;}
.code .me0 {color:#060;}
.code .nu0 {color:#c6c;}
.code .re4 {color:#099;}
.code .sc0 {color:#0bd;}
.code .sc1 {color:#db0;}
.code .sc2 {color:#090;}
.code .st0 {color:red;}
.code .co1,.code .co2,.code .coMULTI {color:gray;font-style:italic;}
.code .kw5,.code .re0,.code .re1,.code .re2 {color:#00f;} |
|
2225 | Greek | Bug Report | Very Low | Greek uses slash for dates | Confirmed | |
| | | 24.10.2016 | 22.11.2016 |
Task Description
Short dates in Greek are represented in the majority of cases with slashes (24/10/2016). Very seldom some people may use the dash form (24-10-2016) and hardly ever the dot form (24.10.2016).
So it would be much appreciated if the slash form were a (working) option because as it is dates are a bit confusing to us, especially in a date-time combination (too many numbers in a not-so-obvious format - brain needs extra time to decode it).
|
|
2317 | User Interface | Bug Report | Medium | Date format wrong | Confirmed | |
| 1.1 devel | | 22.11.2016 | 22.11.2016 |
Task Description
In some parts of the world (primarily the US), the date is viewed as Month/Day/Year. However, all options in the current rc4 build are listed as Day/Month/Year aside from one, which goes ShortWrittenMonth/Day#/Year#.
This is poor from a customer perspective, and can be highly confusing. I can change the date globally to a correct format in the database, but this doesn’t help much as every user can select their own date which has all incorrect formats.
|
|
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.
|
|
2044 | Database Queries | Bug Report | High | Need set_charset for DB connect in config file | Confirmed | |
| 1.0 | 2 | 04.09.2015 | 06.06.2018 |
Task Description
make a option in configuration file
me need set same $db1→set_charset(’utf8mb4’); for my MySQLi
have a problem with national letters
I see this error after i try enter national letters to the summary input text field for create new task
Query {UPDATE `flyspray_tasks` SET project_id = ?, task_type = ?, item_summary = ?, detailed_desc = ?, item_status = ?,
mark_private = ?, product_category = ?, closedby_version = ?, operating_system = ?, task_severity = ?, task_priority = ?,
last_edited_by = ?, last_edited_time = ?, due_date = ?, percent_complete = ?, product_version = ?, estimated_effort = ?
WHERE task_id = ?}
with params {1,1,тестовая задача,<p>sdfsdfdsfsd</p> ,2,0,4,0,1,2,4,1,1441344777,0,0,1,0,2} Failed!
(Incorrect string value: '\xD1\x82\xD0\xB5\xD1\x81...' for column 'item_summary' at row 1)
|
|
2143 | Translations | TODO | Very Low | jscalendar: week start should be monday, ISO 8601 | Confirmed | |
| | | 01.07.2016 | 03.03.2019 |
Task Description
The current jscalendar shows sunday as the first day of the week by default.
Could be modified for a language by adding
// First day of the week. 0 means Sunday, 1 means Monday
Calendar._FD = 1;
js/jscalendar/lang/calendar-XX.js
See also https://github.com/Flyspray/flyspray/commit/f7831b7f6845e237b79da2a68d475f21a24fff72#diff-70a18ca66e215fc5aa282d4c58fed4ab
It should default to Monday as defined by ISO 8601.
https://en.wikipedia.org/wiki/ISO_8601#Week_dates
https://en.wikipedia.org/wiki/Week#Week_numbering
|
|
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.
|
|
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.
|
|
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.
|
|
1990 | User Interface | Feature Request | Low | Roadmap view should also show due dates and sort each v... | Confirmed | |
| 1.1 devel | | 17.04.2015 | 24.04.2015 |
Task Description
Title says all. Small usability fix that will be big
|
|
2071 | Email | Bug Report | Low | New user e-mail validation | Confirmed | |
| | | 14.10.2015 | 14.10.2015 |
Task Description
On flyspray/index.php?do=admin&area=newuser I sucessfuly register user with email ;
I don’t recieve popup with message ‘You did’nt enter valid e-mail address’
After that on new page i receive error:
Completely unexpected exception: Address in mailbox given [;] does not comply with RFC 2822, 3.6.2. This should never happend, please inform Flyspray Developers
|
|
2072 | User Interface | Feature Request | Low | Setting parent task interface is too hidden | Confirmed | |
| | 1 | 16.10.2015 | 16.10.2015 |
Task Description
Hello!
Today i was installed flyspray from git master and found some error.
Any user interface missing any fields to set parent task. Show parent field options was added in “fields when add/edit/view task” field at preferences page for project, but no affect.
Screenshots:
http://joxi.ru/vAWVOKGS9Y812W http://joxi.ru/D2P6dY7h0MnKr3 http://joxi.ru/1A5RGxwSVoM0rE
Flyspray version: Github master branch
|
|
2081 | User Interface | Bug Report | Low | UI for adding comment while editing task doesn't use HT... | Confirmed | |
| | | 29.10.2015 | 06.11.2015 | |
|
2124 | User Interface | Feature Request | Very Low | Default avatar can't be restored | Confirmed | |
| | | 27.04.2016 | 29.04.2016 | |
|
2126 | User Interface | Feature Request | Low | dynamic meta description (was: Change page title) | Confirmed | |
| 1.1 devel | | 17.05.2016 | 17.05.2016 | |
|
2136 | User Interface | Bug Report | Medium | After updating user properties as admin - return to wro... | Confirmed | |
| | | 08.06.2016 | 23.07.2016 | |
|
2207 | Backend/Core | Bug Report | High | Nonpublic project titles and project description exposi... | Confirmed | |
| 1.0 | | 23.09.2016 | 29.09.2016 | |
|
2304 | Database Queries | Bug Report | Medium | Greek letters crash tags | Confirmed | |
| | | 26.10.2016 | 26.10.2016 | |
|
2451 | Backend/Core | Feature Request | Low | Mod: blank Category - user must chose before pressing A... | Confirmed | |
| | | 08.12.2017 | 14.12.2017 | |
|
2561 | Backend/Core | Feature Request | Medium | ability to limit assignee permissions (was:User without... | Confirmed | |
| | | 05.08.2019 | 08.08.2019 | |
|
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 | |
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 | |
|
1529 | Backend/Core | Bug Report | Low | Inactivity-close doesn't work, bug is left open | Maybe | |
| 2.0 | | 07.01.2009 | 24.09.2015 | |
|
1734 | Backend/Core | Bug Report | Low | Add Timezone Selection to Admin Panel | Maybe | |
| 2.0 | | 12.05.2012 | 07.03.2015 | |
|
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 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.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 | |
|
1980 | User Interface | Feature Request | Medium | Tasklist - PDF Export | Maybe | |
| 2.0 | | 19.03.2015 | 26.05.2016 | |
|
2014 | Database Queries | Feature Request | Very Low | Add MS SQL Server as database backend | Maybe | |
| | 1 | 20.07.2015 | 30.07.2015 | |
|
2064 | Notifications | Feature Request | Low | Deadline Alert - so Flyspray can send notifications som... | Maybe | |
| | | 06.10.2015 | 02.12.2015 | |