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

Ronny Voelker wrote:
> 
>> Add WATCHMARKS:
>> ==============
> Here I agree with Jorge and Johannes.
> 
> ...
> 
> 

aehm... Wait a minute. I was not talking about removing user attributes...
For me they can stay as they are. i just have doubts, if the way how
notification
is controlled through user attributes is the best and easiest way we can go.

Currently we can assign as [observer|responsible|whatsoever|...].
Now you get only notified if the assigned userattribute(isn't it a role at
the end?) 
has notification enabled. (we can select [none|to|cc] in the definition
which is per se "wrong"
because the Notification system does not count on emails, but is more
abstract, you might want
to receive notifications via SMS for instance... )

let's assume for a moment, that the role "whatsoever" had notification
disabled.
Now a user gets here and assigns to that role on purpose, because it fits
best. 
He will not get notified although he is associated to the issue.

Another scenario: Assume a user wants to assign himself as Observer, but
just wants
to be able to find this issue when searching "my issues".
He will always get notifications, even if he does not want that.

In both cases it may sometimes be necessary to force notifications when
assigned to a specific
user attribute value (as it is now more or less if cc or to is enabled for
an attribute)...

===

Now assume, we had separated notification from user attributes. Then the
following scenario
would be possible:

- when a user assigns to a role, which is likely to need notifications, his
watchmark is preset
  to "watch this issue". But he can disable that (could be done right
besides the association button)
- when a user assigns to a role, which is likely to need no notifications,
his watchmark is preset to
  "not watch this issue". But he can enable watching if still needed/wanted.

Now we have this scenario: We have the user attributes, which tell about the
relation between user and issue. And we have the watchmark, which tells, if
the user wants to get notified on changes.

===

Of course in todays implementation we can use a trick. Just add following
attributes:

[responsible(always
notify)|observe|observe+notify|whatsoever|whatsoever+notify|...] 

Although it smells a bit, that would work for us here ;-)

So in oprder to proceed i will keep userattributes as they are (for now) and
get back to this, if there is a
real pressure to change that. I will however try to move the "assign as" to
the issue-footer and as an experiment. I guess that is a technical
compromise and i can live with that ;-)

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

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

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