|
2316 | Backend/Core | Bug Report | Low | "wrongtoken" is displayed if the comment box is left si... | Assigned | |
peterdd | | 1 | 22.11.2016 | 29.07.2019 |
Task Description
I understand this is likely due to some sort of XSS CSRF protection, but the delay doesn’t appear to be long enough to be useful for a lengthy comment to be posted. I’ve now lost two detailed comments in our tracker because the software threw everything out and generated a meaningless error.
Further, attempting to do the normal thing and making the browser resubmit the page results in Flyspray throwing “Error #3” something something repeated action and causing a redirect to the homepage.
Surely there has to be a better way to handle this that doesn’t incur data loss?
|
|
2318 | Installer and Upgrader | Bug Report | Low | syntax_plugin required when selected ckeditor in Setup | Requires testing | |
| | | 23.11.2016 | 07.12.2016 |
Task Description
When choosing HTML/CKEditor on the setup screen you are presented with an error stating that syntax plugin cannot be empty.
This is due to the option value being empty:
<select name="syntax_plugin">
<option value="dokuwiki">Text/Dokuwiki</option>
<option value="">HTML/CKEditor</option>
</select>
A suggested fix is to remove the requirement to select an option (since you have to select one or the other anyway).
|
|
2330 | Backend/Core | Bug Report | Low | PHP Notice: Undefined offset: 0 in scripts/index.php o... | Unconfirmed | |
| | | 23.01.2017 | 30.01.2017 |
Task Description
Pretty minor, but seems to show up regularly enough in our logs. The line in question:
$outfile = str_replace(' ', '_', $tasks[0]['project_title']).'_'.date("Y-m-d").'.csv';
|
|
2344 | Notifications | Bug Report | Low | Admins still get noticed for new users even with the op... | Unconfirmed | |
| | | 16.02.2017 | 24.03.2017 |
Task Description
/index.php?do=admin&area=prefs
There’s a checkbox on this menu to toggle whether admins get notices for new user registrations or not. Ours is off, but I’m still getting those notices.
|
|
2345 | Text Rendering | Bug Report | Low | <hr> should be in allowed tags | Unconfirmed | |
| | | 20.02.2017 | 23.02.2017 |
Task Description
Because the hr tag is allowed in the new html comment editor it should be also allowed to display it in the ticket description. class.tpl.php:875 –> just add it here
|
|
2436 | Backend/Core | Bug Report | Low | dokuwiki renderer creates nonunique html-id for h1,h2,h... | New | |
| | | 02.08.2017 | 02.08.2017 |
Task Description
The dokuwiki renderer automatic creates for each h(1-6) tag an html id attribute, but doesn’t ensure that this:
is not used by Flyspray templates
is unique across all tasks (tasklist summary/description mouseover!), id must be unique on a webpage.
Example: id=”footer” and id=”title” are used by the default CleanFS template for example.
title
title
title
id=”title2”
The original intention I think is to make dokuwiki content each h-section linkable, for instance by a “table of contents” at top of a wiki content page. This is currently not used by the dokuwiki integrated in Flyspray, but could be in future.
Possible solution
Add the task_id to the generated id h(1-6) tags, for instance “d1234_footer” “d1234_title”
d - like description
(t1234 used for tags/labels id currently)
|
|
2448 | Backend/Core | Bug Report | Low | error message in eventlog reports | Unconfirmed | |
| | | 26.10.2017 | 29.10.2017 |
Task Description
The last version of Flyspray is simply amazing! it works like a charm :)
This is a small bug report in the eventlog page, that shows this message:
Notice: unserialize(): Error at offset 237 of 808 bytes in /home/elivebugs/bugs.elivecd.org/themes/CleanFS/templates/reports.tpl on line 88 Notice: unserialize(): Error at offset 229 of 796 bytes in /home/elivebugs/bugs.elivecd.org/themes/CleanFS/templates/reports.tpl on line 88
There’s a small screenshot: http://main.elivecd.org/ss/display.php?image=e-59f2541a445543.02125094.jpg
Thank you! Thanatermesis
|
|
2449 | Backend/Core | Bug Report | Low | Unexepted exception on smtp gmail send | Unconfirmed | |
| | | 29.10.2017 | 10.01.2018 |
Task Description
On creating task we got error on event which must send e-mail via “google mail”.
I hoped that in rc6 this will be solved but not. This error was the same on rc4.
|
|
2454 | Backend/Core | Bug Report | Low | PHP warning in admin edit user area | New | |
| | | 15.01.2018 | 15.01.2018 |
Task Description
Since PHP7.2 shows a warning in admin area ?do=admin&area=users&user_id=1234567890, when user_id is set, but no alternative user_name parameter.
Probably related to scripts/admin.php
$id = Flyspray::UserNameToId(Req::val('user_name'));
if (!$id) {
$id = Req::val('user_id');
}
|
|
2491 | Backend/Core | Bug Report | Low | group member links if project manager but not admin | New | |
| 1.0 | | 01.09.2018 | 01.09.2018 |
Task Description
When a user has project manager permissions, but not admin permissions, then on the ‘edit group’ pages like index.php?do=pm&area=editgroup&id=8 the links in the list of users of that group are
index.php?do=admin&area=users&user_id=12345
instead of linking to the users page
index.php?do=user&area=users&id=12345
and a redirect follows with Error #4: You don’t have administrative rights.
|
|
2496 | Email | Bug Report | Low | Notification Mail - Link to the task invalid when quick... | Waiting on Customer | |
| | | 13.09.2018 | 14.09.2018 |
Task Description
Hello,
I’m having an issue on the notification’s mail sent to people when quick-editing a task, more precisely on the link to the task below.
I had this in my older mails : mybugtracker.com/js/callbacks/index.php?do=details&task_id=xxxx
I “corrected” it by adding a str_replace here (see my screenshot), and now it’s good.
Thank you
|
|
2527 | Backend/Core | Bug Report | Low | Database Check »Your mysql supports full utf-8 since 5.... | Unconfirmed | |
| | | 05.01.2019 | 05.01.2019 |
Task Description
Steps done to create the problem: Access /index.php?do=admin&area=checks with a MySQL Version >= 5.5.3
Expected behavior: Flyspray tests for character set and displays »Your mysql supports full utf-8 since 5.5.3. You are using x.x.x and flyspray tables could be upgraded.« when database schema or one table isn’t set to utf8mb4 character set.
Experienced behavior: Flyspray always shows this note, even though character set is correct.
As far as I can tell from the source, a query gets executed to the database (and if I do that manually the result is “utf8mb4, utf8mb4_unicode_ci” for my database), but the result doesn’t get checket, the note is always shown (line 123)
|
|
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.
|
|
2544 | Email | Bug Report | Low | Error when registering new account | Unconfirmed | |
| | | 23.03.2019 | 23.03.2019 |
Task Description
I installed the developer edition.
mysql Ver 14.14 Distrib 5.7.25, for Linux PHP 7.2.15-0ubuntu0.18.04.1 Ubuntu 18.04.2
Admin settings → Allow users to register and send conf. email.
I DID set up email settings thru google and sent a test email. it did work.
After logging out, I tried to register a new account. I filled in details and got the following error: Completely unexpected exception: Expected response code 250 but got code “530”, with message “530 5.7.0 Must issue a STARTTLS command first. u13sm3937813iog.80 - gsmtp " This should never happend, please inform Flyspray Developers
Obviously, the confirmation email was never sent.
I am going to try to manually add a new user. Will update with outcome.
|
|
2549 | User Interface | Bug Report | Low | Oauth register template always shows "Username already ... | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
RC9 running on CentOS LAMP stack
Steps done to create the problem: Set up google as an oauth provider. Have a user click “Sign in with Google” in the login box. User connects their account with Flyspray. Google redirects the user back to Flyspray The return screen (on flyspray) asks for a username.
Expected behavior: No warning about duplicate username should be shown on initial page load since no username was entered yet
Experienced behavior: A warning about the username being already taken is shown.
It appears there is no logic for showing or hiding that warning in register.oauth.tpl
(It would be great if flyspray was able to just use the email as a username to make the UX even better/simpler.)
|
|
2550 | Email | Bug Report | Low | Exception handling sending email notification | Unconfirmed | |
| | | 06.05.2019 | 06.05.2019 |
Task Description
Someone reported this:
Today i tried to report an issue about xxx on the xxx (namely xxx) and the following error message has been displayed:
Completely unexpected exception: Expected response code 250 but got code “451”, with message “451 Error in writing spool file " This should never happend, please inform Flyspray Developers
The issue itself has been created though.
|
|
2559 | Backend/Core | Bug Report | Low | a duplicate close accepted even when missing comment/ r... | New | |
peterdd | | | 29.07.2019 | 29.07.2019 |
Task Description
Closing a task with selected close reason duplicate should warn when there is no comment or FS # id is given in the close comment text field.
The task is closed as duplicate without any further notice. The information to which task it is duplicate or a description (if the problem is logged/handled outside Flyspray) is lost.
Possible solutions
Frontend hints
variant F1 (soft): When duplicate as close reason is selected, a placeholder attribute in the close comment text field could be shown/updated. (maybe as ‘css only’ possible)
variant F2 (harder): Deny sending the form if duplicate selected, but comment text field is empty. and shows warning info. (javascript required, nojs browsers still send form.)
variant F3 (hard): Deny sending the form if duplicate selected and no task id detected in comment text field. and shows warning info. (javascript required)
Backend deny
variant B1 (soft): When request wants close a task with duplicate reason and (cleaned) comment string is empty, deny closing the task and give feedback to user why it was denied.
variant B2 (hard): It requires detecting a task id in the comment field and the first detected task id is taken for referencing as ‘is duplicate of’. Limitation of this is that the duplicate could be also a ticket or something of a complete other system.
|
|
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.
|
|
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
|
|
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
|
|
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.
|
|
1236 | User Interface | Feature Request | Low | Mark Issue As Verified or Unverifiable | Unconfirmed | |
| | 4 | 09.04.2007 | 18.07.2016 |
Task Description
Currently, the Vote functionality provides users a way to say "this issue is important to me". In addition to that functionality, it would be great for users to have a "Verify" ability on open issues; it would provide users a way to say "yes, this happens to me as well".
A "Verified" label would fit nicely right under "Votes", to the right of the label would be "Yes | No", each option being a link. After clicking Yes or No, or if unable to specify (lack of permissions), the text would display "Yes - # | No - # (% verification)" where '%' is the result of ((Yes/(Yes+No))*100).
This feature should not show up on all issues, though. It does not make sense to "verify" a feature request or todo item, for example. When defining task types, the administrator would specify if a type was "Verifiable" by checking a box in a column next to "Show".
If implemented, two great, mini extra features would be:
The ability for the administrator to set the number of "Yes" verifications an issue would need before it was elevated to the next priority, severity, or both (specified by the administrator).
The ability for the administrator to set the number of "No" verifications an issue would need before it was lowered to the previous priority, severity, or both (specified by the administrator).
Both settings should have an option to be incremental (priority / status increased every x verifications) or not (increases once, no matter how many verifications are received); an "Incremental" checkbox would do nicely. Also, a little "Enabled" checkbox next to both settings would be clearer than having zero act as the disable mechanism.
As with voting, a permission should exist to enable or disable this option for a user group. For larger projects, moderators tasked with verifying bugs could be given the permission whereas smaller projects may leave verifications up to the community.
Lastly, a way to send a notification once the number of "Yes" verifications reached a certain value would also be a great addition.
|
|
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
|
|
1485 | User Interface | Feature Request | Low | Additional extended Printview for the Tasks | Planned | |
| 2.0 | | 13.05.2008 | 11.03.2015 |
Task Description
It would be useful to print a list of tasks in a extended version. e.g. All tasks from a programmer with all the details of it.
|
|
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.
|
|
1491 | User Interface | Feature Request | Low | Custom task table columns for individual users | Unconfirmed | |
| 2.0 | 3 | 01.07.2008 | 01.10.2015 | |
|
1518 | Notifications | Feature Request | Low | Show last date/time when a reminder was sent | Unconfirmed | |
| | | 15.11.2008 | 15.11.2008 | |
|
1521 | Backend/Core | Feature Request | Low | Assignees should be able to see and create reminders fo... | Unconfirmed | |
| | | 22.11.2008 | 18.04.2009 | |
|
1539 | Backend/Core | Feature Request | Low | Sitemap.xml Generation | Unconfirmed | |
| 2.1 | 1 | 12.01.2009 | 11.03.2015 | |
|
1599 | User Interface | Feature Request | Low | Implement "Tasks not blocked by other tasks" | Unconfirmed | |
| 2.1 | 1 | 11.08.2009 | 03.03.2013 | |
|
1612 | Backend/Core | Feature Request | Low | Allow Comments by anonymous Users | Unconfirmed | |
| 2.0 | 1 | 20.10.2009 | 17.01.2013 | |
|
1628 | Notifications | Feature Request | Low | Global Notification address | Unconfirmed | |
| 2.0 | | 25.02.2010 | 17.01.2013 | |
|
1670 | User Interface | Feature Request | Low | Assign Key-Shortcuts to form fields | Unconfirmed | |
| | | 04.12.2010 | 04.12.2010 | |
|
1671 | Database Queries | Feature Request | Low | Ability to extract CSV, or Excel | Planned | |
| 1.1 devel | 3 | 18.12.2010 | 08.10.2017 | |
|
1720 | Backend/Core | Feature Request | Low | Better Access Control Lists and User / Group Management | Planned | |
| 1.1 devel | | 01.05.2012 | 20.03.2015 | |
|
1736 | User Interface | Feature Request | Low | Be able to add colors for Task Statuses | Planned | |
| 1.1 devel | | 16.05.2012 | 15.10.2015 | |
|
1748 | Database Queries | Feature Request | Low | Sort by recent activity | Planned | |
| 1.1 devel | | 17.06.2012 | 11.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 | |
|
1766 | Backend/Core | Feature Request | Low | Allow users to choose their favourite theme | Planned | |
| 2.0 | 1 | 16.08.2012 | 04.08.2015 | |
|
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 | |
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 28.04.2016 | |
|
1792 | Backend/Core | Feature Request | Low | Changes from Deprecated 1.0.0 | New | |
| 2.1 | | 13.12.2012 | 03.03.2013 | |
|
1798 | Backend/Core | Feature Request | Low | Bounty System | New | |
| 2.0 | | 13.12.2012 | 06.03.2015 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.2015 | |
|
1811 | Backend/Core | Feature Request | Low | Google Docs/Dropbox Integration | New | |
| 2.0 | | 17.01.2013 | 13.03.2015 | |
|
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 | |
|
1820 | Backend/Core | Feature Request | Low | Merge comments, history, and details | New | |
| 2.0 | | 17.01.2013 | 25.05.2016 | |