|
2453 | Backend/Core | Bug Report | Medium | validate category before storing a new task | New | |
| 1.0 | | 14.12.2017 | 14.12.2017 |
Task Description
Currently the category_id is not checked if the value is legal for the project when a new task is created.
If invalid category_id is sent, deny creating task and show error message and show filled form again.
If no category_id is sent (or empty string) and category select is enabled:
or
implement feature request FS#2451 and show that user should select a category.
|
|
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.
|
|
2635 | User Interface | Feature Request | Medium | improve usability of add/remove tags to/from tasks | Planned | |
| 1.0 | | 13.04.2021 | 23.04.2021 |
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.
|
|
2598 | User Interface | Bug Report | Low | user registration in admin area: "username taken" but t... | Assigned | |
peterdd | 1.0 | | 20.03.2020 | 14.04.2021 |
Task Description
Trying to add a new user having the same email address as an another user in the do=admin&area=newuser section results in
“That username is already taken. You will need to choose another one.”
instead of
“Email address has already been taken”
(I’ve stumbled on this issue because I have an older disabled user with the same email address)
|
|
2609 | User Interface | Feature Request | Low | Add an Effort Description field | Planned | |
| 1.0-rc11 | 1 | 07.05.2020 | 01.04.2022 |
Task Description
It would be nice to have a description field to put a brief note about the work done for a given effort item. This would help when using effort tracking for the purpose of making invoices to a client.
|
|
2636 | Installer and Upgrader | Bug Report | High | Failure to upgrade 1.0-rc9 to 1.0-rc10 (mariadb 10.4.18... | Assigned | |
peterdd | 1.0-rc11 | | 29.04.2021 | 23.07.2021 |
Task Description
I administer a moderate-sized (~14K ticket) 1.0-rc9 instance running on a Fedora 32 host (php 7.4.16, mariadb 10.4.18) Following the upgrade instructions (ie transfer attachments, avatars, flyspray.conf.php) the setup/upgrade tool loads, and prompts me to upgrade.
It churns a while before refreshing the screen, claiming a successful 1.0-rc10 upgrade. However, the upgrade seems to not actually “stick”, because clicking on the “return” button I’m dropped back into the upgrader, which is once again claiming I’m running 1.0-rc9 and prompting me to perform the -rc10 upgrade.
According to Flyspray’s admin ‘checks’ tab:
* PHP 7.4.16 * MariaDB 10.4.18 * default_charset: utf8mb4 * default_collation: utf8mb4_unicode_ci * All tables are ‘InnoDB’
There are no errors logged that I can find, but the upgrade is clearly not working. If I revert to the -rc9 php files, everything continues along as if nothing was done.
Any suggestions?
|
|
2637 | Installer and Upgrader | Bug Report | High | Failure to upgrade 1.0-rc9 to 1.0-rc10 (postgresql 12.6... | Assigned | |
peterdd | 1.0-rc11 | | 29.04.2021 | 05.05.2021 |
Task Description
I administer a small personal (<1K ticket) 1.0-rc9 instance running on a Fedora 32 host (php 7.4.16, postgresql 12.6) Following the upgrade instructions (ie transfer attachments, avatars, flyspray.conf.php) the setup/upgrade tool loads, and prompts me to upgrade.
Unfortunately, the upgrade fails spectacularly, with a reported SQL error that belies what’s actually wrong. Here’s a snippet from the postgresql logs where the upgrade is failing:
2021-04-28 10:33:07.190 EDT [2032049] ERROR: column “attachment_id” of relation “flyspray_attachments” already exists 2021-04-28 10:33:07.190 EDT [2032049] STATEMENT: ALTER TABLE flyspray_attachments ADD COLUMN attachment_id SERIAL 2021-04-28 10:33:07.194 EDT [2032049] ERROR: current transaction is aborted, commands ignored until end of transaction block 2021-04-28 10:33:07.194 EDT [2032049] STATEMENT: ALTER TABLE flyspray_attachments ADD COLUMN task_id INTEGER […and everything else fails because the transaction aborted…]
It appears that the upgrade script is blindly trying to create columns that already exist in the -rc9 database, and postgresql is treating this as a failure. Because the entire upgrade happens within one transaction, this means the entire upgrade fails at the outset and won’t ever succeed.
The way past this specific problem is to make these ALTER TABLE operations conditional (eg “ALTER TABLE flyspray_attachments ADD COLUMN IF NOT EXISTS task_id INTEGER”).
|
|
1222 | Backend/Core | Feature Request | Medium | Workflow engine / Role-based State Transition Rules Eng... | Unconfirmed | |
| | 7 | 25.03.2007 | 05.05.2019 |
Task Description
I have been working with Eventum (http://www.mysql.org/downloads/other/eventum/) for quite sometime now and in contrast, I like Flyspray for its simplicity and practicality. But one thing I badly miss (and something that Eventum scores high) is a Workflow Engine. If not a sophisticated W.E., I (as an Admin / Manager) should be able define role-based state transition rules of the tasks reported in a particular project. For example, I should be able to implement the following scenario:
For a “Developer”, the subsequent tasks from various states. Likewise for other roles
“Developer” should not be able close out the bug reports. He/she can only flag them as implemented. The “Reporter” of the bugs or the “Manager” alone should be able to close out issues
..
.. it will go on like that 
This feature, in my opinion, is very crucial for corporate organizations to give a serious consideration to 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
|
|
1518 | Notifications | Feature Request | Low | Show last date/time when a reminder was sent | Unconfirmed | |
| | | 15.11.2008 | 15.11.2008 |
Task Description
This information is already stored in the table "reminders" in field "last_sent". It might be helpful in some situations, if this date/time would be visible to the user on the reminder list, too.
|
|
1521 | Backend/Core | Feature Request | Low | Assignees should be able to see and create reminders fo... | Unconfirmed | |
| | | 22.11.2008 | 18.04.2009 |
Task Description
In version 0.9.9.5.1 (unfortunately I couldn't select this version in the dropdown list on the left), reminders can only be created and edited by Admins and Project Managers. I recommend to give Assignees the permission to create reminders for themselves. To minimize any programming impact, his may be done as part of the "edit own tasks" permission.
This topic has been reported by Engie as part of Bug #713 for version 0.9.8 as well: "Also it would be useful if a user could create reminder for himself." Although that bug is already closed ("fixed in devel"), this part is not yet solved in the current version.
|
|
1670 | User Interface | Feature Request | Low | Assign Key-Shortcuts to form fields | Unconfirmed | |
| | | 04.12.2010 | 04.12.2010 |
Task Description
Forms should be submittable by using keyboard shortcuts. S for submit. Set-able via the accesskey attribute on HTML inputs.
|
|
1749 | User Interface | Bug Report | Low | Submit form buttons on lower right | Unconfirmed | |
| | | 17.06.2012 | 24.09.2015 |
Task Description
Any form should have its submit button directly below and to the right of the form.
This is most egregious on the New Task page where you have to scroll back up to the top right to submit.
|
|
1791 | Backend/Core | Feature Request | Medium | Ability to merge version, OS, etc | Suspended | |
| | 1 | 12.12.2012 | 12.01.2017 |
Task Description
For example, say I no longer want 1.1, 0.9.9.8, 1.0.0, etc. So want to merge them all into one version 1.0. Same goes for OS, and others
|
|
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.
|
|
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.
|
|
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.
|
|
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)
|
|
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.
|
|
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.
|
|
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.
|
|
1971 | Backend/Core | Feature Request | Low | a field like challenge level or doom level | New | |
| | | 12.03.2015 | 12.03.2015 |
Task Description
We have severity field. We have priority field. We have estimated effort field.
But we don't have a fíeld to see how hard a task is to solve. Something like in doom 3d shooter a face from normal/easy to angry/bloody/very hard.
Imaging you have some people in a company, some base educated, some high educated, some are experts in their field, some do repeating easy tasks.
By adding the ability to set a 'doom level' on tasks this can complete the view over a project in addition to severity,priority,effort.
|
|
1977 | Backend/Core | Bug Report | Low | Weird URL after closing task with reference | Unconfirmed | |
| | | 15.03.2015 | 18.03.2015 |
Task Description
On Mac OS Safari:
I just closed a task and wrote the following into the comment for closing:
"See also F.S.#.14" (of course without the points). When I then click the link in the comment box (below the task details) I'm redirected to: "http:/flyspray.stefan-herz%0Aog.tld/index.php?do=details&task_id=%0A14". No matter if #14 is closed or not. It worked with Firefox.
Any suggestions?
|
|
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
|
|
1985 | Database Queries | Feature Request | Very Low | For developers - testing with huge flyspray data sets | New | |
| | | 24.03.2015 | 16.03.2016 | |
|
1987 | API | Feature Request | Medium | REST API to get metrics from flyspray projects | Unconfirmed | |
| | | 29.03.2015 | 06.10.2015 | |
|
1988 | Installer and Upgrader | Bug Report | Medium | Password Field for Admin | Unconfirmed | |
| | | 02.04.2015 | 12.05.2015 | |
|
1991 | User Interface | Feature Request | Medium | Abillity to drill into progress graph from toplevel vie... | New | |
| | | 17.04.2015 | 24.04.2015 | |
|
1999 | XMPP/Jabber | Feature Request | Medium | jabber xmpp configuration | New | |
| | 1 | 22.06.2015 | 11.02.2017 | |
|
2002 | User Interface | Feature Request | Low | show user role on autocomplete for verification | New | |
| | | 22.06.2015 | 17.10.2019 | |
|
2007 | Backend/Core | Bug Report | Low | time on project overview activity timelines | New | |
| | | 18.07.2015 | 18.07.2015 | |
|
2008 | User Interface | TODO | Low | difference between related tasks and related links | New | |
| | | 18.07.2015 | 18.07.2015 | |
|
2014 | Database Queries | Feature Request | Very Low | Add MS SQL Server as database backend | Maybe | |
| | 1 | 20.07.2015 | 30.07.2015 | |
|
2023 | Notifications | Feature Request | Low | Inform users if reminder is disabled in system settings | New | |
| | | 04.08.2015 | 04.08.2015 | |
|
2025 | User Interface | Feature Request | Low | Adding new tasks is too undiscoverable | Unconfirmed | |
| | | 09.08.2015 | 09.08.2015 | |
|
2029 | Backend/Core | Feature Request | Low | possibility to let a user describe himself | New | |
| | | 12.08.2015 | 18.01.2018 | |
|
2030 | User Interface | Feature Request | Low | show votes of a user on user page | New | |
| | | 12.08.2015 | 15.01.2017 | |
|
2032 | User Interface | Feature Request | Low | replace hardcoded ... 'ellipsis' | New | |
| | 1 | 12.08.2015 | 12.08.2015 | |
|
2034 | User Interface | Feature Request | Low | reduced extended search form when applicable | New | |
| | | 17.08.2015 | 17.08.2015 | |
|
2036 | Backend/Core | Bug Report | Very Low | session timeout | New | |
| | 1 | 21.08.2015 | 12.01.2016 | |
|
2038 | Backend/Core | Bug Report | Low | Jscalendar must be replaced with something else | New | |
| | | 23.08.2015 | 24.08.2015 | |
|
2042 | Backend/Core | Bug Report | Medium | function absoluteURI not using basedir and force_basedi... | Unconfirmed | |
| | 1 | 04.09.2015 | 01.10.2015 | |
|
2045 | User Interface | Feature Request | Low | need add option for can set default Severity and Priori... | Unconfirmed | |
| | 2 | 04.09.2015 | 04.09.2015 | |
|
2046 | User Interface | Feature Request | Low | Grouping in Task List | Unconfirmed | |
| | 1 | 04.09.2015 | 04.09.2015 | |
|
2047 | User Interface | Feature Request | Medium | Inserting images/screenshots from buffer | Unconfirmed | |
| | 1 | 04.09.2015 | 29.09.2015 | |
|
2048 | Backend/Core | Bug Report | Low | error when adding data containing national characters | Unconfirmed | |
| | | 09.09.2015 | 09.09.2015 | |
|
2049 | Backend/Core | Feature Request | Medium | Display login page or customizable page to anonymous us... | Unconfirmed | |
| | | 09.09.2015 | 04.04.2016 | |
|
2052 | Text Rendering | Feature Request | Low | Add Markdown syntax option for task descriptions | Unconfirmed | |
| | | 16.09.2015 | 08.08.2016 | |
|
2057 | Backend/Core | Bug Report | Low | Do not resubmit forms on browser reload button or F5 | New | |
| | | 22.09.2015 | 23.09.2015 | |