Follow-up Comment #7, bug #2335 (project savane):
> Why is it so much complicated to get a public mailing list for public
items
> and a private mailing list for private items?
Because it applies adding yet another way to handle mail notifs. To make it
right, it should be category-configurable, and we would end up with quite
complicated forms.
I propose you a solution that works as of today. If we really want to add
more stuff to these fonctions, I think it will require more thought that just
adding new database fields, new functions and complicating everything.
Maybe some things should be redesigned from the start. For instance, if we
decide that all CC will not be guessed during update but added in the CC list
at item creation, we will have something more manageable. We can then imagine
a simple checkbox with the transition saying "add this in cc permanently".
There are issues with this approach too. That's just one lead, nothing else.
The exclude list has not be implemented to be the cleanest and most useful
thing to deal with private item. It has been implemented to make sure we can
avoid public mailing list to get notifications.
That's not perfect for what you'd like to do but it is doable in the way I
described it below.
> IMHO using category is not clean. And since I'm the unhappy user here, I
> dictate that I don't want the user to even see Category set to
> "Private", that's just an internal tweaking of the tracker,
> "Private" has nothing to do in Category anyway.
Currently, only categories can defines notification list.
We want to change that, it will take more than a dirty hack adding a list for
private thing. Well, we actually can do that. It will just open the door to
more bugs hard to debug.
If we want to do it right, we must make possible that every selectable field
value can imply notification to a specific mailing-list, with the option of
being additional or exclusive
(meaning, for each selectable field value, one should be able to add
notifications or to change the notification list).
Previously in my previous paragraph, I was mentioning usage of the cc list,
this another approach.
But all of this require some thought to make right, and not just adding
endlessly new functions and database fields.
I suggest that you open a task in this regard, for the specific purpose of
such improvement.
> Point 2 is apparently some conflicts in the category change:
Shows that my explanation was not correct :)
- User dont select "private" or "public", it is configured that he cant do
that. Instead, he choose category "Security", and then automatically it is
set to private and "Security" got the relevant notification list already.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?func=detailitem&item_id=2335>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
