#SCB2977 (In progress) Allow only one "assigned to" personell
Hussayn Dabbous <[email protected]> Fri, 3 Jul 2009 20:26:00 +0200 (CEST)
| Newsgroups | gmane.comp.java.scarab.issues |
|---|---|
| Message-ID | <[email protected]> |
*SCB2977 [Enhancement] - Allow only one "assigned to" personell* ------------------------------------------------------------------------------- *Reasons for the changes* ------------------------------------------------------------------------------- - Added Support for "only one assignee" per issue. still needs verification on other platforms. ------------------------------------------------------------------------------- *Attribute changes* ------------------------------------------------------------------------------- - Status: Unconfirmed --> In progress *Comment Hussayn Dabbous* I have added a "multiValue" flag to the attributes table. The key idea is to interpret this flag within the user attributes editor. The flag will also be used for multi value option attributes later (not implemented yet) But for now it works as follows for user attributes: - In the user attributes editor, you can now set the flag "MultiValue" - Whenever a user attribute has this flag set, Scarab takes care to assign one person at maximum to that attribute (within one issue) - So in order to allow only one assignee per issu, just set the userattribute "assigned to" as singleValue attribute. Then Scarab will take care to remove an already assigned user. CAUTION: The original assigned user will not simply be removed. The user will be assigned to "the first multiValue attribute available for the module". Thus in the default settings, the only other available attribute is the "observed by" attribute, which IS m,ulti value. Hence in the default case Scarab behaves in a natural way: If someone "assigns to" an issue, the former assignee changes to "observer". While technicaly no problems occur, if more user attributes are available, ther is a logical problem here It may not always be a good idea to change from "assigned to" to the "first available attribute" There may be workflows which force to make differnet changes. This sort of workflow IS NOT SUPPORTED (yet?) by Scarab! Committed with svn R 10768 ------------------------------------------------------------------------------- Activity generated by Hussayn Dabbous ([email protected]) at 07/03/2009 20:19 [Scarab]: http://www.solitone.org/scarab/issues/id/SCB2977 ------------------------------------------------------ http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=2367864 To unsubscribe from this discussion, e-mail: [[email protected]].