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

> Add WATCHMARKS:
> ==============
> I want everybody to be allowed to set a WATCHMARK to any issue that they can
> view. This checkmark should be decoupled from the personnel section and i
> want to place it right into the left navigation bar, probably as an icon (a
> small eye of course), but for the purists i will make this customizable, so
> that you can have a text-only representation too ;-)
>
> By adding this feature, IMHO the AssignedCC user attribute gets obsolete,
> which is typically used (in the personnel section) to "checkmark" that one
> wants to see all changes on the issue. I also want to make the list of
> watchers only visible to specific roles (associate the visibility to a new
> role permission!)
>

Mmmmhhhh... I don't buy this approach totally. Specializing "Watch"
appart from personnel association features smells strange to me.
Is just a matter of UI? you just need to have a *quick and pretty* way
of user watching issues?


> Workflow modifications
> =================

Not related what we usually call "workflow", is it?

> Constraints on user attributes
> ======================
> I want to add a customizable constraint to the user attributes, which allows
> to define, that a specific user attribute may only be added ONCE to an
> issue, so that you can define, that only one person can be "assigned to" an
> issue at a given time. Any attempt to assign someone else to the issue, will
> remove the former entry (but keep or add the WATCHMARK for that person, see
> above) The constraint shall be settable on module scope.
>

Mmmhhh... sounds reasonably in some context, and easy to implement at
the rissuemodule level.

> Quick Association Button
> ===================

My feedback on this section will definitively depend on the
"watchmarks" problem stated above... will think about it a bit ;)

_
Jorge

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

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