|
1976 | Backend/Core | Feature Request | Low | Save sorting for actual project | Planned | |
| 1.1 devel | | 15.03.2015 | 15.03.2015 |
Task Description
"Sorting by columnXYZ" - possibly in $_SESSION?
|
|
1983 | Backend/Core | Feature Request | Low | Export Roadmap as "Changelog" | Unconfirmed | |
| | | 21.03.2015 | 21.03.2015 |
Task Description
It's a little like "text version". So you could use this exported changelog within a new release.
I think good was:
Only resolved tasks ordered by date (but of course without displaying the date) and only public accessible tasks
Without task number ("FS#...")
A download function via button
|
|
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
|
|
2000 | User Interface | Feature Request | Low | Responsible persons column view | New | |
| 1.1 devel | | 22.06.2015 | 09.09.2015 |
Task Description
In the task list the responsible persons are shown as "first person name, +n" where n are the count of further responsible persons.
I think this can be done a bit better.
Ideas:
show as it is now, but on css :hover show all persons
use initials like "CR FS JM" for Cristian R., Florian S., Jordan M. and on css :hover show a list with the full names, this can make the column width a bit smaller.
-
|
|
2002 | User Interface | Feature Request | Low | show user role on autocomplete for verification | New | |
| | | 22.06.2015 | 17.10.2019 |
Task Description
When adding peoples with the autocompleter the name itself is not always enough, especially with a growing number of registered users.
We now have the avatar icon as helper, but for quick verification it would be easier to see also the role of the user in the current project to identify the right user account.
( The red rectangle at peterdd autocomplete row is from a broken avatar upload, ignore it for this task, see FS#1979 instead .. )
|
|
2005 | Backend/Core | Feature Request | Low | one account, several authentications | New | |
| 1.1 devel | | 18.07.2015 | 18.07.2015 |
Task Description
Currently it seems a user needs two accounts to login by normal user-password and oauth2 login with facebook,g+ etc.
Better would be if a normal username-password registered user could connect a oauth2-login with his existing login.
|
|
2009 | User Interface | Feature Request | Low | Edit task flow | New | |
| 2.0 | | 18.07.2015 | 07.08.2016 |
Task Description
Currently only a small portion of adjustements on a task is available in the “edit task” view.
To add or modify stuff in the current tab sections (comments, related tasks, notifications, effort tracking,..) a user must go from edit task to view task page.
This not optimal for work flow.
To solve this quite much changes are needed. Because currently they are different http requests each with its own checks and request anwsers.
|
|
2010 | User Interface | Feature Request | Low | effort tracking widget | New | |
| 2.0 | | 18.07.2015 | 18.07.2015 |
Task Description
If effort tracking started by a user on a task, maybe we should add a small widget on the page, so user sees which tasks are currently running as his own time tracking.
|
|
2013 | User Interface | Feature Request | Low | personal task list column selection and positioning | New | |
| 2.0 | | 20.07.2015 | 06.10.2015 |
Task Description
Currently the appearence of the task list table is configured system wide for all project view and project wide for project task list views.
Even more fancy and for power users would be if the user can set his own project column list view preferences for projects.
While the project columns for the task list are configured by "visible_columns" we could use the project wide "visible_fields" as allowed columns the user may configure as his personal preference. If the user doesn't configure his own list, the project default list is used. The user should have the option to reset to project default. (e.g. empty personal "visible_fields" )
In this case the description for setting "visible_fields" on the project management configuration page must be adapted too.
Probably a new table required something like:
CREATE TABLE {user_projects} (
user_id int,
project_id,
columns varchar(255) DEFAULT '',
);
or
CREATE TABLE {user_projects} (
user_id int,
project_id,
columns varchar(32) DEFAULT NULL,
sort int,
);
|
|
2022 | Backend/Core | Feature Request | Low | default or auto options for some settings | New | |
| 1.1 devel | | 03.08.2015 | 15.01.2019 |
Task Description
Some project and user settings should be able to set back to its default or 'auto' option.
flyspray or project wide task list length, currently hard coded to 250
user tasks_perpage setting
user notifytype
user timezone
user language (system/project and auto (browser detection) selectable)
...
|
|
2023 | Notifications | Feature Request | Low | Inform users if reminder is disabled in system settings | New | |
| | | 04.08.2015 | 04.08.2015 |
Task Description
There are 5 possible cases that IMHO should be handled more user friendly:
There is no cronjob for the reminder (schedule.php) setup → Reminders are never sent
Reminding is disabled in the global settings → Reminders are never sent
Reminder setting 'email' only → Reminders are only sent to users who set their notification setting to 'email' or 'both' and setup an email address
Reminder setting 'jabber' only → Reminders are only sent to users who set their notification setting to 'jabber' or 'both' and setup a jabber address
Project notification setting not set → ??? (research...)
If notification is disabled (1. or 2.), the notification tab on 'task details page' should adapt to that I think. (by css style or message or tooltip)
If notification is restricted to only one notification channel, the current user should be informed on notification tab on 'task details page' if he would receive notifications with his current notification settings.
|
|
2025 | User Interface | Feature Request | Low | Adding new tasks is too undiscoverable | Unconfirmed | |
| | | 09.08.2015 | 09.08.2015 |
Task Description
The Flyspray Manual ( http://www.flyspray.org/manual/ ) does not even hint of it, and as long as i am not logged in there's no indication anywhere in the interface that i would eventually get to do it after i manage to log-in.
In fact, i've come here to learn how to use your software, considering the fact that the site where it was deployed did not provide much help. And after i logged in into that site ( http://www.uzbl.org/bugs/ ) i still don't see any "add new task" option. That's IMO a discover-ability fail, and it originates in your own design: disabled features should not be hidden, lest users think you didn't bother to code such features. Also, you say i shouldn't report bugs against versions earlier than 0.9.9.7, but how do i know which version of Flyspray are they using?
|
|
2029 | Backend/Core | Feature Request | Low | possibility to let a user describe himself | New | |
| | | 12.08.2015 | 18.01.2018 |
Task Description
This could be done by a textarea field (like comment text or task description) on the myprofile page and stored in a new field (of type text for instance) in the user table.
This allows the user to introduce himself to the other users.
Should be restrictive, for instance only simple text allowed, no html or tags.
|
|
2030 | User Interface | Feature Request | Low | show votes of a user on user page | New | |
| | | 12.08.2015 | 15.01.2017 |
Task Description
On the user page
/index.php?do=user&area=users&id=* or /index.php?do=user&area=users&id=*&project=1 or /index.php?do=user&area=users&id=*&switch=1 (project switch select)
an info could be shown how many votes a user has given.
Maybe show the tasks on mouse hover (:hover) if permission to view them exists.
Needs to be considered:
Show count only for current project or all projects? (project param is optional on user page)
counts of hidden, closed or restricted projects (user permission)
How to handle votes of private tasks?
Show votes of closed tasks too? (votes on closed tasks should don’t count for max votes per project)
When personal “max votes per project” (open tasks) is active, this is of more value.
|
|
2032 | User Interface | Feature Request | Low | replace hardcoded ... 'ellipsis' | New | |
| | 1 | 12.08.2015 | 12.08.2015 |
Task Description
Thomasz wrote:
The other thing that I cannot find how to make the text to be visible in the whole column (as with the summary I get the ... at some point of the text).
The root of this is found in scripts/index.php in function tpl_draw_cell():
case 'summary':
$value = tpl_tasklink($task, utf8_substr($task['item_summary'], 0, 55));
if (utf8_strlen($task['item_summary']) > 55) {
$value .= '...';
}
break;
We live in a world now, where the view port ranges from 320 pixel width mobile screens up to 4k+ wide tv screens, the amount of columns is configurable from minimal to all available fields of a task. We currently let the browser automatic decide how wide he renders each column depending on table content and available window size.
Well, that ellipsis problem can be handled at different levels:
motivate the task creators to use short task summary if possible (e.g. show a hint/tooltip when typing the summary gets over a limit, in our case the hardcoded limit is 55. ). Short task topic/summaries are easier to read/scan for the users.
replace the hard ellipsis by a pure css solution, that adapts to users browserwindow size/space in in the columns for summary
drop the ellipsis thing complete, task summary always shown full length, table rows adapt in height automatically.
Possible CSS solution:
|
|
2034 | User Interface | Feature Request | Low | reduced extended search form when applicable | New | |
| | | 17.08.2015 | 17.08.2015 |
Task Description
If a project has no versions defined yet and there are also no 'global' versions defined, there is not need for displaying the version selects.
Same for categories. If no categories in project and no global categories then no need for displaying a cat select.
Maybe a tooltip/hint in the extended search form to inform the user that the fields were hidden for that reason.
|
|
2045 | User Interface | Feature Request | Low | need add option for can set default Severity and Priori... | Unconfirmed | |
| | 2 | 04.09.2015 | 04.09.2015 |
Task Description
need add option for can set default Severity and Priority of new creating tasks
|
|
2046 | User Interface | Feature Request | Low | Grouping in Task List | Unconfirmed | |
| | 1 | 04.09.2015 | 04.09.2015 |
Task Description
Need add view of grouping in Task List by Category
|
|
2052 | Text Rendering | Feature Request | Low | Add Markdown syntax option for task descriptions | Unconfirmed | |
| | | 16.09.2015 | 08.08.2016 |
Task Description
“Markdown is a lightweight markup language with plain text formatting syntax designed so that it can be converted to HTML and many other formats using a tool by the same name.[6][7] Markdown is often used to format readme files, for writing messages in online discussion forums, and to create rich text using a plain text editor.” - https://en.wikipedia.org/wiki/Markdown
|
|
2054 | Backend/Core | Feature Request | Low | Fields for csv export choosable like for task list | New | |
| 2.0 | | 17.09.2015 | 31.12.2017 |
Task Description
Currently the task list columns are used, which are choosed by admin or project manager for the task list view.
|
|
2059 | Backend/Core | Feature Request | Low | usage of github automated/webhook notifications | New | |
| | | 24.09.2015 | 24.09.2015 |
Task Description
We have no API yet for Flyspray.
But someone could write a simple php-file that can be called by a github.com auto notification, whenever:
Github.com provides the configuration of such notification for a possible target like
https://bugs.flyspray.org/api/github.php
or
https://bugs.flyspray.org/api/github.php?project=1
in the settings of a project.
What the file needs:
import some of the existing Flyspray classes from includes/
config or load the secrets that are provided by github.com in the setup for the automatic notification
check that secrets and more for authentication and authorization of requests coming from github.com
-
take actions on the results of that message parsing like making adding comment or modifying a task status
|
|
2064 | Notifications | Feature Request | Low | Deadline Alert - so Flyspray can send notifications som... | Maybe | |
| | | 06.10.2015 | 02.12.2015 |
Task Description
splitted from FS#1697 as own task
|
|
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
|
|
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.
|
|
2118 | User Interface | Feature Request | Low | Show overview of existing tags for users | Assigned | |
peterdd | 1.1 devel | | 09.04.2016 | 26.10.2019 |
Task Description
At several places it could be useful to let the user view available tags:
When editing a task a toggle popup could show a list of selectable and existing tags.
I found several nice vanilla-js-multiselect-with-autocompletion scripts, but none yet that still works at a basic level when javascript is turned off.
My plan is now:
Keep the current basic input text field for input tags and show current assigned tags like exampletag1;exampletag2;exampletag3 separated by ‘;’ that is sent to the server when saving the task and server handles evaluation of that string (validation, duplicates, removed, added, creating new tags if allowed for current user)
A CSS only toggle that shows available tags that can be assigned (works even with js turned off), similiar to other places within Flyspray like advanced search toggle.
If js turned off, the user must type the tag - not as fancy, but at least works. (I thought also about using a html select with multiple=”multiple” attribute, but was not convinced due styling not possible in modern browsers without js)
If js is enabled, more fancier stuff is possible:
The input text field is hidden by display:none and instead the styled tags are shown.
The current added tags also get a little x to remove a tag by clicking it. The content of the hidden input text field is updated to reflect the current editing status. (click eventlistener)
A generated text input field for typing with autocompletion list shown of matching availbale tags. An unknown tag is added to the list if user is allowed to create tags. Clicking a item in the autocompletion list adds the tag and resets the autocompletion input text field for the next autocompletion action.
The tags within the toggle list with all available tags get also a click event listener, so clicking it adds them to the hidden text input.
Not sure yet if an added tag should be removed from the all available tags list or just make an CSS indication that a tag is still added, currently I tend to keep the list untouched, just highlight used tags of the task.
Make the list of tags searchable for the advanced search. added with FS1.0-rc10 by just using search key words also for searching list_tags table.
|
|
2126 | User Interface | Feature Request | Low | dynamic meta description (was: Change page title) | Confirmed | |
| 1.1 devel | | 17.05.2016 | 17.05.2016 | |
|
2127 | User Interface | Feature Request | Low | overhaul task detail page layout | New | |
| | | 20.05.2016 | 25.05.2016 | |
|
2190 | Backend/Core | Feature Request | Low | enable move of a closed clask to other project without ... | Researching | |
| | | 06.08.2016 | 06.08.2016 | |
|
2193 | User Interface | Feature Request | Low | Edit a comment while seeing task details and other comm... | New | |
| | | 07.08.2016 | 08.08.2016 | |
|
2216 | Notifications | Feature Request | Low | Add slack integration (webhook) | Unconfirmed | |
| | 1 | 18.10.2016 | 25.10.2018 | |
|
2308 | User Interface | Feature Request | Low | improve user management for admins | New | |
| | | 27.10.2016 | 13.02.2017 | |
|
2325 | User Interface | Feature Request | Low | big image attachments: fit to browser window width in L... | New | |
| | | 10.01.2017 | 11.01.2017 | |
|
2327 | Backend/Core | Feature Request | Low | visibility-option for private tasks | Unconfirmed | |
| | | 15.01.2017 | 17.01.2017 | |
|
2346 | Backend/Core | Feature Request | Low | Custom css inheritance | Unconfirmed | |
| | | 20.02.2017 | 23.02.2017 | |
|
2427 | Backend/Core | Feature Request | Low | allow hotlinking (direct links) to uploaded files | Unconfirmed | |
| | | 07.03.2017 | 09.03.2017 | |
|
2430 | Backend/Core | Feature Request | Low | User dependency on project | Unconfirmed | |
| | | 16.03.2017 | 20.03.2017 | |
|
2439 | Backend/Core | Feature Request | Low | Clone a Project | New | |
| | | 15.09.2017 | 15.09.2017 | |
|
2440 | Backend/Core | Feature Request | Low | Option to disable tag feature | New | |
| | | 15.09.2017 | 15.09.2017 | |
|
2451 | Backend/Core | Feature Request | Low | Mod: blank Category - user must chose before pressing A... | Confirmed | |
| | | 08.12.2017 | 14.12.2017 | |
|
2459 | User Interface | Feature Request | Low | Attachments on/off and max size setting in Admin Toolbo... | Unconfirmed | |
| | | 16.02.2018 | 03.03.2018 | |
|
2520 | Notifications | Feature Request | Low | Send a notification for a new task in slack integration... | Unconfirmed | |
| | | 24.10.2018 | 30.03.2020 | |
|
2522 | Backend/Core | Feature Request | Low | email vs username login issues | Researching | |
| | | 31.10.2018 | 02.11.2018 | |
|
2531 | Translations | Feature Request | Low | detect usage of translation keywords | New | |
| | | 10.01.2019 | 19.03.2019 | |
|
2534 | Backend/Core | Feature Request | Low | Private projects | Unconfirmed | |
| | | 16.01.2019 | 18.01.2019 | |
|
2535 | Backend/Core | Feature Request | Low | new optional Flyspray setting: add new users automatica... | New | |
| | | 16.01.2019 | 21.01.2019 | |
|
2548 | User Interface | Feature Request | Low | CSS grid layout for task details page type | New | |
| | | 05.05.2019 | 05.05.2019 | |
|
2575 | Backend/Core | Feature Request | Low | ability to view and reset Flyspray default settings | New | |
| | | 19.09.2019 | 19.09.2019 | |
|
2581 | User Interface | Feature Request | Low | replace bitmap icons of default theme | New | |
| | | 31.10.2019 | 07.12.2019 | |
|
2595 | Notifications | Feature Request | Low | Notifications to message platforms | Unconfirmed | |
| | | 05.03.2020 | 26.03.2020 | |
|
2602 | Documentation | Feature Request | Low | https://github.com/flyspray/flyspray instead of https:/... | Waiting on Customer | |
| | | 21.04.2020 | 09.10.2020 | |