All Projects

ID Project Category Task Type Severity Summary Status Opened by Opened Progress
 2638 FlysprayUser InterfaceTODOLow Add tag helper also for the add new task form Closedpeterdd10.05.2021
100%
Task Description

Now that the edit task page has the tag helper it is logic to add the tag helper also to the add new task form.

2635FlysprayUser InterfaceFeature RequestMediumimprove usability of add/remove tags to/from tasksPlannedpeterdd13.04.2021
70%
Task Description

Integrate the selectpure javascript to the new task and edit task form.

By default there is a text field where tag names are separated by ‘;’ character.

Selectpure could instead show the tags with their visual layout with a little ‘x’ inside on the right side for removing a tag and autocomplete when typing a tag name to show existing tags from the flyspray_list_tag-table as possible selections.

Instead implemented a CSS and raw javascript solution with a single taghelper.js without any dependancies.

A button beside the tag input text field toggles a list of available tags for the current task, depending on the project and settings.

Still TODO

  • styling of added tags
  • highlight tags that would be removed when the task will be saved.
  • highlight tags that would be added when the task will be saved.
  • highlight tags that are attached to the task in the available taglist.
  • highlight tags that are added to the task in the available taglist.
  • optimize layout for this feature.
 2631 FlysprayBackend/CoreInformationLow ljljklj Closedpeterdd11.03.2021
100%
Task Description

lhlkjlkjlkj

2629FlysprayBackend/CoreBug ReportLowactivating history tab sends same request 2 timesNewpeterdd11.03.2021
0%
Task Description

There should be only one request to

js/callbacks/gethistory.php when activating the History tab

The request is made:

  • on mousedown event
  • on click event

So holding down the tab sends the first request and releasing sends the second request.

2625FlysprayUser InterfaceTODOLowavoid password manager popups in admin prefs areaNewpeterdd10.02.2021
0%
11 Task Description

We must teach browsers not to use some input fields in the admin prefs area to offer to store it in their password manager.

Steps to reproduce:

  1. Login with Firefox as admin into Flyspray. (Maybe other browsers behave same)
  2. Go to admin prefs area (top right gear icon)
  3. Click link somewhere else (so leaving admin prefs page)
  4. Firefox browser pops up password manager as it detected some password input fields on admim prefs setting page. But in this case this is not wanted.

Either by using different input field names where the browser does not assume it is a login password field or find input field attribute to tell them.

auto-complete="off"

is not working anymore in browsers for password fields.

webbrowser: Firefox 85.0.2

Popup probably triggered by the password fields for configuring Email and XMPP notification: smtp_pass and jabber_password input fields. Firefox heuristic is too stupid to detect that these are for server configuration, not user login fields!

Neither

autocomplete="new-password"

nor

autocomplete="one-time-code"

attribute helped.

Stubborn Firefox ..

 2624 FlysprayBackend/CoreBug ReportHigh fatal error with PHP8 and syntax_plugin html (ckeditor) Closedpeterdd10.02.2021
100%
Task Description

The used get_class_methods($classname) function now throws exception in PHP8 when the class does not exists (or couldn’t be found).

grep -rin4 get_class_methods 
class.tpl.php-1006-	public static function render($text, $type = null, $id = null, $instructions = null)
class.tpl.php-1007-	{
class.tpl.php-1008-		global $conf;
class.tpl.php-1009-
class.tpl.php:1010:		$methods = get_class_methods($conf['general']['syntax_plugin'] . '_TextFormatter');
class.tpl.php-1011-		$methods = is_array($methods) ? $methods : array();
class.tpl.php-1012-
class.tpl.php-1013-		if (in_array('render', $methods)) {
class.tpl.php-1014-			return call_user_func(array($conf['general']['syntax_plugin'] . '_TextFormatter', 'render'),
--
class.tpl.php-1036-    public static function textarea($name, $rows, $cols, $attrs = null, $content = null)
class.tpl.php-1037-    {
class.tpl.php-1038-        global $conf;
class.tpl.php-1039-
class.tpl.php:1040:        if (@in_array('textarea', get_class_methods($conf['general']['syntax_plugin'] . '_TextFormatter'))) {
class.tpl.php-1041-            return call_user_func(array($conf['general']['syntax_plugin'] . '_TextFormatter', 'textarea'),
class.tpl.php-1042-                                  $name, $rows, $cols, $attrs, $content);
class.tpl.php-1043-        }
class.tpl.php-1044-

Previously it just returned null as also documented on php.net! :-/
https://www.php.net/manual/en/function.get-class-methods :

In case of an error, it returns null.

So either php guys update their source code or documentation. Netherless a workaround is needed.

2620FlysprayBackend/CoreTODOMediumPHP8 compatibilityNewpeterdd26.11.2020
20%
2 Task Description

PHP 8.0 is now released (2020-11-26) and Flyspray should be made compatible with it.

  • Replace removed and deprecated functions with alternatives in our source code.
  • Upgrade used libraries or make used libraries compatible:
    • post github issue or pull requests for ADODB
    • upgrade used dokuwiki or make changes in our integration (probably just review our as official dokuwiki project contains too much stuff we do not need and changed much)
    • review used geshi
    • upgrade our swiftmailer version to PHP8 compatible version
    • upgrade our oauth2-client stuff to PHP8 compatible version
2606FlysprayDatabase QueriesFeature RequestLowduedate column sort asc in tasklist should put unset du...Newpeterdd02.05.2020
0%
1 Task Description

When a tasklist contains the duedate column and the user sorts by duedate ascending, the tasks that do not have a duedate set should not be listed first. Instead they should be listed after the tasks with duedates.

This way a user can see the task with the earliest duedate first instead of seeing a bunch of probably not so important tasks without duedates set.

 2594 FlysprayBackend/CoreTODOHigh pagination of user list Closedpeterdd23.02.2020
100%
1 Task Description

For Flyspray installations with many users (several thousands) a pagination of the user list in the admin area is required.

2000 users no problem to display (aside the PHP max_input_vars limit which is only 1000 by default, so maybe not all checked checkboxes are handled.)

More users might send your mysql to long running blocking queries creating temp tables … bad!

(I killed them by watching show processlist; and kill id; on mysql console.)

 2593 FlysprayDocumentationTODOLow document special search string characters Closedpeterdd15.02.2020
100%
Task Description

+ is a special character in the search string. The behavior was introduced in 2006, but to my knowledge was never documented anywhere.

Also the usage of % and _ for SQL LIKE pattern matching that can be used by Flyspray searches should be documented.

Note: The matches of such search strings with placeholders are not used by the “highlight search string matches in results”-feature.

 2586 FlysprayBackend/CoreTODOLow PHP7.4 Closedpeterdd12.12.2019
100%
3 Task Description

PHP 7.4 is out now and a few things should be done to make Flyspray work well with it.
Nothing really breaks, but a view deprecation warnings should be fixed.

Flyspray source itself: Just a few new notices, most are yet fixed in the master branch.

Watching the PHP7.4 compatibility of dependencies defined by composer.json:

  • ADOdb/ADODb: 5.21 for PHP 8 done
  • swiftmailer/swiftmailer: We still use 5.* branch, so either do quickfix for a notice in a fork or upgrade/rewrite our integration to the 6.* branch. 6.* is PHP7+, so stay with 5.* branch for now. If Swiftmailer does not fulfill requirements, consider switching to PHPMailer for FS1.1+
  • ezyang/htmlpurifier: 4.13 OK
  • thephpleague/oauth2-client: unknown, we still use 0.13, last real source change was Nov 2018, to upgrade requires rewrite of integration into Flyspray and there is low demand for OAuth2.
  • dapphp/securimage: seems to be OK, but not maintained anymore (we could patch it if there occur problems in future)
  • jamiebicknell/sparkline: OK, but probably obsolete for us in future due
    • still annoying problems with our github/travis tests (problem of travis, not sparkline itself)
    • better solution (interactive hover infos, scales, screen size adaptive) by Flyspray source planned
 2585 FlysprayUser InterfaceTODOMedium Upgrade CKEditor to 4.16 Closedpeterdd02.12.2019
100%
3 Task Description

To fix some other open tasks, an update of the CKEditor4 files is probably the best way.

Basic preset

Starting with CKEditor4 ‘Basic’ preset, evaluate every additional Plugin before adding them to the config.

Because the selection of plugins starts with the ‘Basic’ preset, some configs are disabled in the resulting config.sys like the ‘Strike’ button or the Copy/Paste functionality.

I am also evaluating the possibilities to make some of the options configurable within the Flyspray configuration. It is probably required to analyze if a setting applies to only CKEditor syntax or would be also by used for installs using dokuwiki syntax/engine.

I can also imagine enable/disable features based on Flyspray user permissions. (but that requires not only CKEditor config, but also server side changes like HTMLpurifier settings.)

Plugins

The previous contained CKEditor 4.4.7 probably hat the standard preset used.

Following I keep track of plugins we should add to the basic preset. This list is growing/edited until the final config that ships with Flyspray is found.

Mentions

This would enable choosing a user by their username, like @peterdd.

Requires writing an extra php file for retrieving a matching list of users, that respects current user permissions and status of users (like not fetch disabled users).
This extra php file could be also used for the editor textareas with a dokuwiki toolbar.

Auto Grow

This is just a promising usability improvement. No scrollbars needed when writing longer texts.

Turns just typed urls like https://www.flyspray.org into real links (like dokuwiki does it when rendered on page.)

Baloon Toolbar

This just sound like a promising usability improvement. Not tried yet. Only add when there is use case (other plugins usability profit from it) for Flyspray.

Blockquote

Probably required because existing Flyspray installs had it too and citing a comment/text snippet should be also able.

Code Snippet

Probably requires deeper look how secure integrate with server side cleanup (HTMLpurifier).

Format

h1-h6 and other tags. Probably required as previous Flyspray versions used that too. (TODO: What happens to old content with h1-h6 tags when editing with a CKEditor without the Format plugin?)

Also configure it to accept only tags useful for within Flyspray. (see also server side configuration of HTMLPurifier)

Remove Format

Existing Flysprays had this too and probably a good thing when the user can cleanup their word/whateverwhere pasted stuff cleaned before HTMLpurifier does it server side too with maybe surprises to the end user.

Show Blocks

Gives the user some confidence on command if his current editing has the right/intended structure.

Well, that missing is one of the reasons why I hated WYSIWYG or wannabe WYSIWYG editors in the past. Uncertainty by the end user, and pain for the admin/webmaster when he sees the garbage stored in the database (endless spans and other garbage tags partly wrong nested by just pasting from Word documents.)
(little bug in CKEditor 4.13.0: doesn’t expand the area with plugin Auto Grow enabled)

Source Editing Area

Useful for people that can read HTML or are responsible to fix things.

Theme selection

Probably use a CKEditor source maintained Moona-Lisa or Moona as these are easier to modify their color themes like auto light/dark mode browser detection or base colors that match the theme.

Moona Color currently has issues and not maintained by CKEditor guys.

Languages

Just choose all languages available in the CKBuilder.

Probably we need to adjust the CKEditor to use the users Flyspray language settings too. I changed my language to french in a test install but the CKEditor still shows german user interface. (probably detected by browser http request headers)

Compare that the used language abbreviations work together between files in lang/ of Flyspray and that of CKEditors. (Flyspray: lang/pt_br.php vs. CKEditor: js/ckeditor/lang/pt-br.js)

2581FlysprayUser InterfaceFeature RequestLowreplace bitmap icons of default themeNewpeterdd31.10.2019
20%
Task Description

I played with adding a dark mode color theme to the default CleanFS theme.

To make the dark theme just simple exchange some colors, the bitmap icons should be replaced with alternatives.

Easiest would be using the fontawesome font icons as Flyspray still uses them and they can simply get a css color assigned.

Examples

  • caret of tasklist
  • the ‘select all’ icon of tasklist, but also used at some more locations.
  • some icons in the Flyspray main toolbar (Overview, Tasklist, Event log, ..)
  • the black calendar icons for date selects
  • maybe the file type icons for attachments

Editors

  • Dokuwiki toolbar fixed in devel for Flyspray 1.0-rc10
  • CKEditor: some modern CKEditor themes support color/dark mode, I will probably choose the moona-lisa theme as default.
2577FlysprayUser InterfaceFeature RequestVery Lowdistinguish between anonymous reporter and deleted userNewpeterdd18.10.2019
0%
Task Description

When a user is deleted from Flyspray, their opened tasks, closed task and task comments are then shown as Anonymous Submitter, the same way as anonymous reporters (not really anonymous, just that user does not have login account, but usually their email address is stored within that task data).

Currently just the entry from users table are deleted when a user is deleted. Their internal user_id integer is still within tasks and comments fields, and maybe some other tables too. So there is not a ON DELETE SET NULL rule or something like that applied. As it is just an autoincremented number by the system, this is not personal data imho and should be no problem for GDPR, but gives Flyspray the ability to distinguish between anon reporters and deleted users. Well, we could also look if there is an email address within task table entry for notification of anonymous reporter, but there are also tasks possible that have no user_id nor an email address.

It might by useful to present that information differently like deleted user or showing the info differently like icon + title-tooltip with explanation.

Also interesting what happens with mentions of a deleted username in a comment or task description. (see FS#2322)

The user isn’t in database, but deleting that now gone user should not modify tasks or comment where that username was mentioned I think.
But what if another user registers under that now gone username? In that case that new user would inherit that mentions. Probably we can ignore that edge case as there will be not much things will happen with an old mention in old tasks/comments.

2575FlysprayBackend/CoreFeature RequestLowability to view and reset Flyspray default settingsNewpeterdd19.09.2019
0%
Task Description

Motivation

Over the years the count of possible Flyspray configuration options has grown. Meanwhile there are ~60 global Flyspray settings stored in the prefs database table in contrast to only 14 entries of the 0.9.7 (not 0.9.9.7!) version from around 2005. But each configuration setting might add a little to the feeling of overwhelming when there are too much switches, buttons, checkboxes and probability of a misconfiguration raises due misunderstood or overseen settings.

But Flyspray still aims to be easy to use and work with while being accurate and customizable.

Proposal

Having a way to view the description and default value of each option would probably give people administrating a Flyspray installation a better understanding of each setting and confidence in making good decisions for their use case.

With the flyspray-install.xml file within the setup folder we yet have an elegant solution that is waiting to unlock its power!

Unfortunately the setup/ folder requires (until now at least) to be removed after install or upgrade. So we need a way to keep the flyspray-install.xml of the installed version. A trivial way would be to copy it to the include/ directory after any install or upgrade, but also other solutions could be.

Keeping the flyspray-install.xml could making following features easier:

  • Reading default value of prefs setting. That could be shown for example as css title attribute /tooltip for each setting in the matching admin forms.
  • Reading default value and field description of any table field using the descr feature of ADOdb xmlschema03.
  • Comparing the real database structure with the table structures in flyspray-install.xml . This could be useful if someone extended or fiddled with database/tables to compare with official Flyspray releases. Or for developers to compare if an database upgrade went well and as intended.
  • Having the description of a setting or database field contained within the flyspray-install.xml is good at one place and the information is not spread around like in an external manual/wiki that maybe get unmaintained, not in sync with the application or get even lost over the years.
  • Using the xml format makes a migration easier (in a broader context, to Flyspray or away from Flyspray)
  • Using the descr tag could be used to hold information which field(s) of a database table is/are foreign key field(s) pointing to primary key field(s) of another table, even if ADODB xmlschema03 does not support it yet. Would generating database schema diagram directly from flyspray-install.xml possible. (instead of manually painting it that gets outdated when structure changes)

Things to take care:

  • ADOdb and xmlschema03 does not handle table comments and field comments yet. The descr tag so is there only used when looking into the .xml file, but it does not appear in the real database schema. To make this happen, there is a good portion of contribution to the ADOdB project required (making pull request, but also get them reviewed, tested, accepted and released with a ADOdb stable release)
  • ADOdb xmlschema03 does not define or handle foreign key constraints. Adding that would require a substantial amount of constribution to get it working reliable for all supported databases that could use foreign key constraints.
  • limits of table comment length, field comment length depend on database type and database version
2573FlysprayBackend/CoreTODOLowadd rel nofollow,ugc,.. settingsNewpeterdd14.09.2019
20%
1 Task Description
  1. Find a good configuration name just reuse relnofollow as used by dokuwiki
  2. Find a good translation keyword for that config relnofollow
  3. Find a good translation keyword for config description (title attribute)

Goes into prefs table as it is sitewide configuration.

As first implementation a simple checkbox should be ok. Should be on the tab with other spam handling stuff like captcha configuration.

Is enabled by default (1).
Adapt setup xml files, upgrade procedure.


	
2572FlysprayUser InterfaceTODOLowadd link attributes ugc and nofollow to user generated ...Newpeterdd13.09.2019
0%
Task Description

no task description

 2569 FlysprayBackend/CoreBug ReportLow after deleting the last existing project some php warni ...Closedpeterdd02.09.2019
100%
Task Description

PHP: 7.2.*

If you just delete the last existing project in a Flyspray installation (like directly deleting the default project after install), Flyspray shows some php warnings on the following pages like:

Notice: Undefined variable: prs in /***/index.php on line 215
Warning: array_filter() expects parameter 1 to be array, null given in /***/index.php on line 215
Warning: Invalid argument supplied for foreach() in /***/includes/class.backend.php on line 1548
Warning: Invalid argument supplied for foreach() in /***/themes/CleanFS/templates/header.tpl on line 17
Warning: count(): Parameter must be an array or an object that implements Countable in /***/themes/CleanFS/templates/links.tpl on line 43
Warning: count(): Parameter must be an array or an object that implements Countable in /***/themes/CleanFS/templates/links.tpl on line 119
Warning: count(): Parameter must be an array or an object that implements Countable in /***/themes/CleanFS/templates/links.tpl on line 141

After creating at least 1 new project again all is back to normal. Neverless these warnings should be correctly fixed. (not just by silencing php warnings)

 2560 FlysprayBackend/CoreBug ReportLow do not allow close task with reason duplicate referenci ...Closedpeterdd29.07.2019
100%
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.

2559FlysprayBackend/CoreBug ReportLowa duplicate close accepted even when missing comment/ r...Newpeterdd29.07.2019
0%
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.
2554FlysprayUser InterfaceTODOLowkeyboard shortcuts help box should adapt to current pag...Newpeterdd06.06.2019
0%
Task Description

The shortcuts help infobox should adapt to the current page type.

So when in editing a task for instance, the n (next task) and p (previous task) shortcuts are not available for a good reason. Listing them there with same priority as other keys then is not helpful.

The simpliest solution is probably putting some if-statements depending on the $do variable into CleanFS/templates/shortcuts.tpl ..

2553FlysprayUser InterfaceTODOLowintelligent accesskey shortcut helper dependent of OS, ...Newpeterdd06.06.2019
50%
1 Task Description

The HTML accesskey attribute feature is differently accessible dependent of operating system, web browser and web browser configuration, and users keyboard layout and user language.

By taking advantage of the User-Agent HTTP header value provided by default by web browsers, Flyspray could better know of what kind of keyboard and browser the user sits in front off and show the key combinations for the accesskey feature that best fits the users environment.

2550FlysprayEmailBug ReportLowException handling sending email notificationUnconfirmedpeterdd06.05.2019
0%
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.
2548FlysprayUser InterfaceFeature RequestLowCSS grid layout for task details page typeNewpeterdd05.05.2019
0%
Task Description

Layouts from 320 pixel mobile portrait, tablet sizes and up to 4k monitor landscape mode using

@media queries

Mockups required not only for different sizes, but also different project configurations, user permissions, and task relations.

Should look ok whatever project configuration is done or how weird a task description is.

On wider screens the comments could be beside the task description for instance.
Or some tabs or menus could be shown directly instead of grouping in the tabs.

2536FlysprayBackend/CoreFeature RequestMediumstore session in Flyspray databaseNewpeterdd21.01.2019
0%
2 Task Description

Currently the sessions are stored by the webservers default settings.

Having this sessions under control by Flyspray by storing it in the database has following advantages:

  1. Allows handling of all sessions of a user by Flyspray.
  2. Providing a session management for each user. The user can see on which devices he is currently logged in and could also force a logout on selective devices.
  3. A forced logoff of all or some user sessions is easy implementable for admins.
  4. Statistics about how many users and who is logged in. (user status: hide always, online, offline, do not disturb, ..)
  5. Could make onpage-notifications easier to implement.
  6. .. ?

Disadvantages:

  1. A potential unknown security bug in Flyspray that could lead to reading a session db table could leak informations like who is currently online/active and make further attacks more focused or makes session takeover easier.
  2. .. ?
2535FlysprayBackend/CoreFeature RequestLownew optional Flyspray setting: add new users automatica...Newpeterdd16.01.2019
0%
2
 2532 FlysprayBackend/CoreBug ReportMedium spaces before or after a single word search gives too m ...Closedpeterdd11.01.2019
100%
1
2491FlysprayBackend/CoreBug ReportLowgroup member links if project manager but not adminNewpeterdd01.09.2018
0%
2454FlysprayBackend/CoreBug ReportLowPHP warning in admin edit user areaNewpeterdd15.01.2018
0%
2453FlysprayBackend/CoreBug ReportMediumvalidate category before storing a new taskNewpeterdd14.12.2017
0%
 2452 FlysprayBackend/CoreBug ReportHigh deprecated functions since PHP7.2 Closedpeterdd13.12.2017
100%
1
2444FlysprayInstaller and UpgraderInformationLowcomposer hits memory limitsNewpeterdd04.10.2017
0%
2441FlysprayBackend/CoreBug ReportMediumrefactor dokuwiki image tagsNewpeterdd15.09.2017
0%
 2440 FlysprayBackend/CoreFeature RequestLow Option to disable tag feature Closedpeterdd15.09.2017
100%
1
2439FlysprayBackend/CoreFeature RequestLowClone a ProjectNewpeterdd15.09.2017
0%
3
2436FlysprayBackend/CoreBug ReportLowdokuwiki renderer creates nonunique html-id for h1,h2,h...Newpeterdd02.08.2017
0%
21
2337FlysprayDocumentationInformationLowFlyspray ThemesNewpeterdd02.02.2017
0%
418
2332FlysprayBackend/CoreBug ReportMediumCSV export filename filteringNewpeterdd24.01.2017
0%
2
2325FlysprayUser InterfaceFeature RequestLowbig image attachments: fit to browser window width in L...Newpeterdd10.01.2017
0%
32
 2313 FlysprayBackend/CoreInformationMedium different composer.json for different php versions? Closedpeterdd17.11.2016
100%
2308FlysprayUser InterfaceFeature RequestLowimprove user management for adminsNewpeterdd27.10.2016
30%
2
2221FlysprayInstaller and UpgraderInformationLowNotices on install with PHP7Newpeterdd24.10.2016
50%
1
2215FlysprayText RenderingBug ReportLowwrong output of Geshi syntax highlighting for xml codeNewpeterdd17.10.2016
0%
11
 2213 FlysprayBackend/CoreBug ReportMedium fix warnings with PHP7 Closedpeterdd17.10.2016
100%
 2195 FlysprayBackend/CoreTODOHigh Release Flyspray 1.0-rc2/rc3/rc4 Closedpeterdd15.08.2016
80%
2193FlysprayUser InterfaceFeature RequestLowEdit a comment while seeing task details and other comm...Newpeterdd07.08.2016
0%
2190FlysprayBackend/CoreFeature RequestLowenable move of a closed clask to other project without ...Researchingpeterdd06.08.2016
0%
2188FlysprayBackend/CoreBug ReportVery LowIt should not possible to relate a task to itselfNewpeterdd01.08.2016
0%
 2159 FlysprayBackend/CoreTODOHigh fresh registered user accounts created spam tasks Closedpeterdd04.07.2016
100%
2
2143FlysprayTranslationsTODOVery Lowjscalendar: week start should be monday, ISO 8601Confirmedpeterdd01.07.2016
10%
2
Showing tasks 1 - 50 of 133 Page 1 of 3

Available keyboard shortcuts

Tasklist

Task Details

Task Editing