|
1843 | Backend/Core | Feature Request | Low | Attach 1 ticket to multiple projects | Maybe | |
| 2.0 | | 07.03.2013 | 06.03.2015 |
Task Description
As title says
|
|
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.
|
|
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.
|
|
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
|
|
2139 | User Interface | Feature Request | Very Low | Add project setting of popular used programming languag... | New | |
| 1.1 devel | | 17.06.2016 | 17.06.2016 |
Task Description
This is at the moment just a bit brainstorming ..:
Let the project administrator define what source code languages are used/popular in a software project and dependend of that setting prefer/promote that languages at the dokuwiki editor buttonbar.
This requires probably an additional database field in the flyspay_projects table (if just used for dokuwiki that should be ok)
If thinking further like Filter me all software projects that may ontain CSS code on the projects overview, a m:n-table setup is thinkable. But thats maybe overengineering..
Or can we use the existing tag-feature for that and just ‘tag’ projects with tags?
|
|
2599 | Backend/Core | Information | Low | add post request on new task creation | Unconfirmed | |
| | | 30.03.2020 | 12.04.2021 |
Task Description
I’m currently using flyspray 0.9.9.7
I want to make a little integration of our flyspray installation into slack.
I want make a POST request when a “new task is created”
Any experiment guy can help here ?
1. Where is the best place to achieve this quickly as “hack hardcode” 2. Im not php developer, is there any php lib in flyspray todo quick POST request without installing any additional lib.
|
|
2572 | User Interface | TODO | Low | add link attributes ugc and nofollow to user generated ... | New | |
| | | 13.09.2019 | 13.09.2019 |
Task Description
no task description |
|
2629 | Backend/Core | Bug Report | Low | activating history tab sends same request 2 times | New | |
| | | 11.03.2021 | 11.03.2021 |
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.
|
|
1991 | User Interface | Feature Request | Medium | Abillity to drill into progress graph from toplevel vie... | New | |
| | | 17.04.2015 | 24.04.2015 |
Task Description
From the overview view for a project the progress charts should be large and show dates so can have a better sense for absolute progress and then when click it should see it full size going back to start of project and showing dates.
|
|
2575 | Backend/Core | Feature Request | Low | ability to view and reset Flyspray default settings | New | |
| | | 19.09.2019 | 19.09.2019 |
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
|
|
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.
|
|
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.
|
