“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra
This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!
Do not issue bugs reports against versions earlier than 0.9.9.5
Security problem? Check the security section.
FS#1090 - Hide some fields and add a javascript link to show theses hiden fields
Attached to Project:
Flyspray - The bug killer!
Opened by Ludovic Gasc (GML) - Monday, 30 October 2006, 21:16 GMT+1
Last edited by Florian Schmitz (Floele) - Sunday, 12 August 2007, 10:10 GMT+1
Opened by Ludovic Gasc (GML) - Monday, 30 October 2006, 21:16 GMT+1
Last edited by Florian Schmitz (Floele) - Sunday, 12 August 2007, 10:10 GMT+1
|
DetailsTo help new users to use flyspray, it would be useful if it’s possible to hide some fields, and add a javascript link “advanced fields...” to show theses hidden fields. |
This task depends upon
FS#218 - Extensibility mechanism for adding new task properties
View Dependency Graph
View Dependency Graph
Closed by Florian Schmitz (Floele)
Sunday, 12 August 2007, 10:10 GMT+1
Reason for closing: Will Not Implement
Additional comments about closing: 1.0 allows you to remove any fields you don't need.
Sunday, 12 August 2007, 10:10 GMT+1
Reason for closing: Will Not Implement
Additional comments about closing: 1.0 allows you to remove any fields you don't need.
This task is the duplicate of
FS#728Thanks to close this task.
Hide what fields? Flyspray is a pretty simple BTS as these things go. Hide much more and it’ll just be description and and status. :)
It’s not a dupe of
FS#728. It would beFS#218rather.Maybe it’s not necessary to hide the fields, but I definitely think that giving more structure to their list (the left-hand side of the task box) would help to quickly spot the field(s) one is interested in. E.g. splitting it into 2-3 groups, something like this but obviously more nicely formatted: