|
1964 | Documentation | Feature Request | Low | On page documentation | New | |
| | | 11.03.2015 | 11.03.2015 |
Task Description
This is a parent task for all small helping or explaining tooltips that can be maybe added where approriate.
Many people don't like reading external documentations, which sometimes often is also not up to date with the current used version.
If you are doing something in Flyspray and you don't know exactly how it works or have to be done rigth and you must look at documentation, it breaks your workflow.
The best case is if its all perfect intuitive and you don't have to read any help texts. But in the case of more complex operations or things that do many things behind the scene a helping tooltip or explanation can give you a mental map and more trust into what the tool is doing.
|
|
1962 | Backend/Core | Feature Request | Low | SMS notification - sending notifications via sms same a... | New | |
| | | 11.03.2015 | 02.12.2015 |
Task Description
moved from FS#1697 into a separate task.
|
|
1961 | User Interface | Feature Request | Low | show new notifications in flyspray | New | |
| | | 11.03.2015 | 11.03.2015 |
Task Description
similiar to facebook.com or github.com show new unread notifications on the topbar.
|
|
1960 | Backend/Core | Bug Report | Medium | foreign key relations between versions and tasks | New | |
| | | 09.03.2015 | 13.08.2015 |
Task Description
It seem that when deleting a version entry in a project, that tasks that have this version assigned are still connected to this deleted version. For example FS#1222 (on 2015-03-09).
There are several options to solve such things:
The same for other assignments for tasks.
This issue is similiar to the massop issue: (https://github.com/Flyspray/flyspray/issues/130)
|
|
1959 | User Interface | Feature Request | Low | Add vote from tasklist | Planned | |
| 1.1 devel | | 09.03.2015 | 09.03.2015 |
Task Description
Well, title is self explanatory, but adding a vote button in the overview in task list whould be nice. And that backedup with an option to enable it or not in the admin panel
Idea by Wertandrew
|
|
1958 | User Interface | Feature Request | Low | Preselect values for event log view | New | |
| | | 09.03.2015 | 09.03.2015 |
Task Description
Most (or even all?) of the selectable events should be preselected in the selection list.
|
|
1957 | User Interface | Feature Request | Low | automatic temporary storing while writing/editing task | Researching | |
| | | 09.03.2015 | 12.03.2015 |
Task Description
If I write a task and press the back button in the brower and go forward again, my expection is that the text I wrote is still existing, even if I didn't save it.
It is frustrating losing a well thought issue editing and having it to rewrite.
|
|
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:
|
|
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
|
|
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
|
|
1924 | Backend/Core | Bug Report | Low | Better errors messages on email error | New | |
| 1.1 devel | | 11.07.2014 | 06.03.2015 |
Task Description
When entering the wrong SMTP information and then adding a user through Multiple New Users page, the error message is bad. It just says 'this should never happen'. Instead, we need to detect that it is an SMTP authentication error and report that issue to the user more clearly.
|
|
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 |
Task Description
Ability to click field to edit ticket
TODO: return handler if request ok or fail.
TODO: also clicks on label should trigger show form.
Maybe the whole “click to active for editing this field” to one click too much. So if the user has the rights to edit the value the form input or action button should be shown when viewing a task. All other people just see the value if they have the right to view the value.
|
|
1882 | Email | Bug Report | Medium | Error with email notification | Planned | |
| 2.0 | | 22.12.2013 | 08.04.2016 |
Task Description
Hello,
First of all, thanks for this great tool, very user friendly. I'm informing you as requested ("This should never happend, please inform Flyspray Developers" :)) because I'm getting this error message:
[Completely unexpected exception: Connection could not be established with host http://ssl0.ovh.net/ [php_network_getaddresses: getaddrinfo failed: Name or service not known #0] This should never happend, please inform Flyspray Developers]
I set up the SMTP configuration (SSL) with information provided.
Enclosed in PHPinfo configuration, if it helps.
Thanks
|
|
1876 | Backend/Core | Feature Request | Low | Add wiki page tab | Planned | |
| 2.0 | 1 | 26.09.2013 | 06.03.2015 |
Task Description
It will quite useful to have wiki page for project.
|
|
1875 | Backend/Core | Feature Request | Medium | Ability to mark project as completed | Maybe | |
| 1.1 devel | 1 | 26.09.2013 | 12.10.2015 |
Task Description
Currently projects in Flyspray are active or set inactive.
It will be great to archive project if finished or abandoned. In this case it will not be shown in project overview page and project navigation combo.
|
|
1871 | Backend/Core | Feature Request | Low | Restricted Task Types Based on Group | Maybe | |
| 2.0 | | 19.07.2013 | 06.03.2015 |
Task Description
I have a public bug tracker and would like to have a TODO like task, except restricted so only the developers can set the task type to TODO, while the general reporters can just submit bug reports or feature requests.
|
|
1868 | Backend/Core | Feature Request | Low | One issue for multiple components | Maybe | |
| 2.0 | | 22.06.2013 | 12.11.2015 |
Task Description
Hi,I would like to see a enhancement, where you can submit/edit and assign it to multiple components, as it needs work from multiple sides.
For example: A user asks for a new object to be visualized. This includes work of the GUI designers and altering internal core structures. For internal management, I would like to label this for both teams.
|
|
1866 | Backend/Core | Feature Request | Low | API for automatically report a bug | Maybe | |
| 2.0 | 1 | 08.05.2013 | 06.03.2015 |
Task Description
Actually you can't automatically add a bug report. Or i haven't found it. In a first time a simple report via email or webservice could be great.
- Project Name - Message - System - Version - Status –> New - Priority → Normal - Category –> On a new category (created by default) : 'Automated report bug'
Sorry for bad grammar, i'am not english.
|
|
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.
|
|
1858 | Backend/Core | Feature Request | Low | Clone Tasks and Projects | Maybe | |
| 2.0 | | 02.04.2013 | 15.09.2017 |
Task Description
My workplace is piloting Flyspray for an internal project and one feature that my boss was asking about was the ability to clone tasks and projects.
We have reoccurring simultaneous projects that contain a large number of testing tasks, and tasks dependent on other tasks, which makes starting up a new project very tedious. If it was possible to clone the contents of a task, or an entire project, we could create template tasks/projects that would really speed up the workflow.
|
|
1857 | User Interface | Feature Request | Low | Login and then submit new task | Researching | |
| 2.0 | | 27.03.2013 | 06.03.2015 |
Task Description
Hello, when I wanted to use Flyspray to manage request from non-technical customer, I found one missing feature:
I have "report a problem" link on devel version of web site. But to submit new task, it is necessary to login into Flyspray.
It would be nice if there was an URL with login form if user is not logged in and "add new task" form if he is logged in.
Example scenario: - Customer visits devel site after some time and finds some problem. He wants to report it. - Customer clicks "report a problem" on the devel site and Flyspray is opened. - Customer now see some wierd error message and has no idea what is wrong. If anonymous reports are allowed, he sees the form, but cannot upload screenshots and he must enter his e-mail address.
How it should be: - Customer visits devel site after some time and finds some problem. He wants to report it. - Customer clicks "report a problem" on the devel site and Flyspray is opened. - Customer sees login form and (if anonymous reports are allowed) there is also "add new task" form below the login form. - Customer clicks "login" (password is saved in browser). - Customer now can fill report with all the comfort.
|
|
1856 | Backend/Core | Bug Report | Medium | Wrong timezones | Researching | |
| | 3 | 27.03.2013 | 06.03.2015 |
Task Description
Hello, when selecting timezone in user profile, it only offers offset based timezones. It should offer timezones like "Europe/Prague", instead, because in summer it is UTC+2 and in the winter UTC+1. Also UTC is the same as GMT.
Using offsets will cause invalid future and past times when crossing daylight saving or when something other changes.
Adding daylight checkbox is not enough and will cause additional troubles. Just use names and store them as ENUM in database, not offset. This problem is pretty complicated and the only solution is to use names and let libraries to solve it for you.
Thank you.
|
|
1849 | Backend/Core | Feature Request | High | Installer Overhaul | Planned | |
| 1.1 devel | | 15.03.2013 | 15.07.2016 |
Task Description
The application installer needs an overhaul, all strict notices fixed and the associated dependant tasks resolved.
|
|
1847 | User Interface | Feature Request | Low | Make default theme responsive | Planned | |
| 1.1 devel | | 14.03.2013 | 16.10.2015 |
Task Description
I think it is time to think about an theme optimizied for mobile Devices.
We will not maintain several themes. We will review the current CleanFS theme to make it responsible instead.
|
|
1844 | Translations | Feature Request | Low | Czech translate | Waiting on Customer | |
| | | 08.03.2013 | 12.12.2019 |
Task Description
Hello, sorry my english - i’m translated Flyspray ver 0.9.9.7 to czech language - its attached
Petr
|
|
1843 | Backend/Core | Feature Request | Low | Attach 1 ticket to multiple projects | Maybe | |
| 2.0 | | 07.03.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 | |
|
1834 | Backend/Core | Feature Request | Low | user profile page | Maybe | |
| 2.0 | | 25.02.2013 | 06.03.2015 | |
|
1823 | Backend/Core | Feature Request | Low | Comments with edit changes | Planned | |
| 2.0 | | 30.01.2013 | 06.03.2015 | |
|
1820 | Backend/Core | Feature Request | Low | Merge comments, history, and details | New | |
| 2.0 | | 17.01.2013 | 25.05.2016 | |
|
1819 | Backend/Core | Feature Request | Low | Communicate via email | Planned | |
| 2.0 | 3 | 17.01.2013 | 18.10.2016 | |
|
1818 | Backend/Core | Feature Request | Low | Git/SVN/CVS Integration | Planned | |
| 2.0 | 2 | 17.01.2013 | 12.08.2015 | |
|
1812 | Backend/Core | Feature Request | Low | Multiple email addresses | Planned | |
| 1.1 devel | | 17.01.2013 | 30.12.2015 | |
|
1811 | Backend/Core | Feature Request | Low | Google Docs/Dropbox Integration | New | |
| 2.0 | | 17.01.2013 | 13.03.2015 | |
|
1809 | User Interface | Feature Request | Low | Searching closed tasks by Reason for closing | Maybe | |
| 2.0 | | 17.01.2013 | 06.11.2015 | |
|
1798 | Backend/Core | Feature Request | Low | Bounty System | New | |
| 2.0 | | 13.12.2012 | 06.03.2015 | |
|
1792 | Backend/Core | Feature Request | Low | Changes from Deprecated 1.0.0 | New | |
| 2.1 | | 13.12.2012 | 03.03.2013 | |
|
1791 | Backend/Core | Feature Request | Medium | Ability to merge version, OS, etc | Suspended | |
| | 1 | 12.12.2012 | 12.01.2017 | |
|
1783 | Notifications | Feature Request | Medium | Create account for non-logged user automatically | Planned | |
| 2.0 | | 27.11.2012 | 07.03.2015 | |
|
1782 | Backend/Core | Feature Request | Low | Custom fields on task | Planned | |
| 2.0 | 3 | 27.11.2012 | 07.01.2020 | |
|
1774 | Backend/Core | Feature Request | Low | Email Layout | Maybe | |
| 2.0 | | 11.10.2012 | 20.07.2015 | |
|
1772 | Backend/Core | Feature Request | Low | Different kinds of votes | Maybe | |
| 2.0 | 1 | 23.09.2012 | 09.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 | |
|
1760 | Backend/Core | Feature Request | Low | Column 'last commenter' in tasks list view | Maybe | |
| 2.0 | 2 | 27.07.2012 | 25.10.2016 | |
|
1753 | Backend/Core | Feature Request | Medium | Usergroup Restriction: Only View Summary | Confirmed | |
| 1.1 devel | 2 | 20.06.2012 | 27.06.2016 | |
|
1751 | Backend/Core | Feature Request | Medium | Default to show all in Event Log | Confirmed | |
| 1.1 devel | 1 | 20.06.2012 | 09.02.2016 | |
|
1749 | User Interface | Bug Report | Low | Submit form buttons on lower right | Unconfirmed | |
| | | 17.06.2012 | 24.09.2015 | |
|
1748 | Database Queries | Feature Request | Low | Sort by recent activity | Planned | |
| 1.1 devel | | 17.06.2012 | 11.03.2015 | |
|
1737 | Javascript | TODO | Low | Javascript Overhaul | New | |
| 1.1 devel | 1 | 25.05.2012 | 24.02.2016 | |
|
1736 | User Interface | Feature Request | Low | Be able to add colors for Task Statuses | Planned | |
| 1.1 devel | | 16.05.2012 | 15.10.2015 | |