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

Jorge Uriarte wrote:
> 
>> 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 ;-)
>>
>> ...
>>
> 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?
> 
> 

The highest ranked criticism on Scarab from our customer is 
how to assign personnel and how to deal with observing issues.
They currently have to do that on the personnel tab and from what
i call the workflow (which you may name "click flow" if you like) the
assigning and reassigning of personnel needs improvement. Maybe it is
because of how we deal with these user attributes: 

In our setup we have setup these user attributes:

- observed by (which is in principle equivalent to "watch that issue")
- assigned To (which is for us the person who is currently responsible)

assume, the assignedTo user has finished his task. Then he forwards the
issue
to another personnel. what has he to do ?:

1.) change myself from assignedTo to observedBy
2.) add the next responsible as assignedTo or change his state from
observedBy to assignedTo
3.) go to the attributes section and change state from "in progress" to
"forwarded to"

We need the whole set of states and personnell associations due to the
specific workflow of the
customer, which goes on behind the scene.
====
Now this was the borth of the whole idea of reworking the personnel tab.
I myself am pretty much influenced by how Jira handles this topic. There you
can
set a watchmark to any Issue you like, just by checkmarking the "watch this
issue".
And that is pretty convenient and fully matches the needs in our usecase. 

How it is handled behind the scenes is another story. Now look at the
current implementation of
the NotificationManager. Everything is built up on user attributes, which
even can be absent.
Have you ever tried to setup a module, without the user attributes
AssignedTo and assignedCC ? 
You will end up with stack traces... 
So we need some rework here anyways. And since personnel is essential to
Scarab usage, why not 
establish the "watchmark" right into the kernel, where this mark is the one
which controls, who gets
notified, and who not. Then we still can use the user attributes to add more
subtle informations like
assignedToAnalysis, assignedToFixing, assignedToQA, all customizable in
whichever way you like...


Jorge Uriarte wrote:
> 
>> Workflow modifications
>> =================
> 
> 
> Not related what we usually call "workflow", is it? 
> 

as i said above, workflow here means, what users do
when they deal with personnel chages ;-) Is there a better
wording to use ?

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

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

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