Changes:
Should Start On: ven 19.11.2004 � 01:00 -> ven 19.11.2004 � 00:00
Should be Finished on: sam 19.11.2005 � 01:00 -> sam 19.11.2005 � 00:00
_______________________________________________________
Follow-up Comment #17:
I am sorry but I doubt you can convince me that a comment is more important
than the field that defines the status, priority (etc) of an item. Comments
are technically here to justify changes made on these fields. These fields are
what matter most. We are talking about an issue tracker.
Does rfc822 defines issues trackers notifications? What matters is not to
print data, it is also to make it understandable, even by non-geeks. I'm not
sure we can find something easier to understand than the current
$field: $old_value -> $new_value
What surprises you is maybe the formatting. But from what I know, it is more a
nuisance to a user to deal with stuff like
$field: $oldvalue -> $new_value
$thisfieldislonger: $huthisislongtoo -> $short
$v: $a -> $a
"would not remind me much about this task within a few weeks."
I guess that when the title does not speak for itself, one have to follow the
link (which is nowadays quite trivial). Just like if someone was receiving a
mail on a mailing-list.
"I do not dispear to see / code a mail interface to the trackers i>
the>future."
But such interface could be an additionnal interface, not a replacement.
Anyway, sending full information in each notification defeat the concept of
"notification". I guess a mail interface would provide a way to get the full
details of an item, given a specific command.
"The drawback is that web users may get bored to see a lot of quoting in the
comments; in this case, maybe we should provide a way to filter such quoting
for web users. If we get super-clever when comparing the quoted texts, we
could even provide an auto-threaded wiki-discussion-style way to present the
follow ups, but that can wait :)"
It's getting complicated. :)
But currently, I'm quite satisfied with the content of the notifications
(minus the bug "ven 19.11.2004 � 06:00 -> ven 19.11.2004 � 00:00"), I just had
to take care at first to read the title field, something I forgot. The
previous notification was too dense that I was anyway usually looking at the
item on the web interface anytime I needed context.
So:
- me alive, "changes" will stay before "comments" :))
- anything that could remind the user would be good
- somewhere, the project name is missing
I think I'm going (right) to make a test with the "Changes:" and "Follow-up
Comment #16:" section title, adding ", project $name, bug $nnn:" to the first
section shown on the mail. That would address the 3rd point.
_______________________________________________________
This item URL is:
<http://gna.org/task/?func=detailitem&item_id=1074>
_______________________________________________
Message post� via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
