Re: Proposal for a significant change in the personel section!

May last post might have been a bit unclear, so here some more thoughts:

1.) I think, we can implement the abstract "Notify me upon changes" right
into Scarab without the need of user attributes. I think, this feature is so
essential, that we can indeed leverage it to the kernel.

2.) I do not exactly know, what we can do with user attributes besides what
we do in the personnel settings, i.e. assignTo and AssignCC. So maybe due to
lack of understanding user attributes in their whole glory, it does make
sense to me to separate the "notify on change" from the user attributes.

So if we would separate notification from user attributes, the WATCHMARK
immediately makes sense and IMHO it is an easy and very clean
implementation. We even could reimplement the dependencies between user
attributes and the WATCHMARK. e.g. something like this (customizable on user
attribute scope?):

assignedTo forces the Watchmark to be set.
assignedCC presets the Watchmark, but the user can remove it.

But all of this may be complete nonesense, if user attributes are something
completely different. So  my question at the end (should have been at the
beginning): What are user attributes for ?

Hussayn
-- 
View this message in context: http://www.nabble.com/Proposal-for-a-significant-change-in-the-personel-section%21-tp23899951p23901609.html
Sent from the Scarab - User mailing list archive at Nabble.com.

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=456&dsMessageId=2359972

To unsubscribe from this discussion, e-mail: [[email protected]].