I have the feeling that you are focused on reducing the number of lines to improve lisibility. It seems to me that this works only on items with are nearly empty. It would already be a different story with items with comments of more than 10 lines, which include sections/subsection, bits of code (in this case, your separator is likely to be near invisible).
95% of my tracker items are dread simple (from, assigned, status, comment), and a bunch of them come from Gna! administration. After 11 months, I am still bad (ie. slow) at deciphering notification emails: was the ticket closed? answered? reassigned? I clearly do not have the whole picture of Savane usage, it's just my end user impression and opinion. But my main idea is to be more 'adaptative'. We have the good old 'fully featured vs. minimalist' fight :).
What about the idea of having empty values for most ancilliary fields ? From the form interface, it could even help: I find myself scanning the whole fields to check if I answered/updated them correctly (and regularly miss!). That would not be the 'Unknown' value (it means 'I want to know' for me), that would be the 'Unused'/'I do not care' one. I would be quicker if I had not to read all values and evaluate them, but rather simply see if there's a value or not.
For instance, the 'Effort' field is empty as a default, and it looks equivalent to me to omit to display it, or display it with its empty value. Only the latter is noisy.
Oh, it would not work with the date items, these are rightfully pre-filled. I don't have any elegant solution to say that I don't need them. I didn't mean it to be simple :)
_______________________________________________ Savane-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/savane-dev
