Pavel Janík wrote:
From: Jörg Jahnke <[EMAIL PROTECTED]>
Date: Mon, 13 Feb 2006 16:25:08 +0100
Hi,
Hi,
> what about sending out an email to the QA representative of the CWS
> once the CWS gets integrated?
well, yes, this is another possibility. And its implementation is much
easier ;-)
It´s indeed much easier. We would just need to send one email to one
person including the links to issuezilla.
> below, or perhaps a list of links to the single issues. The advantage
> I see with this method is that only the person doing the QA for the
> CWS (i.e. whom it concerns) is notified and others don't get
> "flooded" with (for them) useless information.
If the issue is assigned to you, it means you were the QA for it, so in
fact it is the same, no? And as it is the same, using your method to get
the data is much easier :-)
Well, it is not quite the same as originally suggested. The difference
is that not every task owner would get an email, just the QA
Representative of the Childworkspace and that it would be done for each
Childworkspace integrated instead of collecting information from every
ChildWorkspace integrated as a new Milestone into the MasterWorkspace.
First question is wether it is better that only the QA Representative
gets an email or wether each individual Task Owner would get his/her
individual mail just about the issues owned. Deciding on this question
is also a matter of deciding on workflow: Should the QA Rep. have the
global overview about the process of rechecking and closing tasks after
the Childworkspace has been integrated and delegate work to other QA
members involved in the same Childworkspace or is that not needed and
better if just everyone involved in QA for a Childworkspace gets a note
with his/her own iusses thus automating the task of delegating QA work
for this step.
Second question is if it´s better to have one mail per new Milestone or
if it´s enough or even better to have one mail per Childworkspace.
Technically it would be simpler to implement a mail per Childworkspace
and I can also see a process workflow argument for doing it that way as
the people doing QA might already have had individual unreleated test
plans for each Childworkspace and working on one email would thus mean
working on one subtask releated to one set of testplans. An argument
against that would be that this would probably mean more emails. The
technical reason for doing it per Childworkspace is that EIS currently
only get´s notified about the state change of each Childworkspace but
not notified when all Childworkspaces have been integrated and the
milestone is ready.
The other thing suggested in this thread, that is automatically entering
some kind of comment into the issue would be technically difficult to
implement and would IMHO generate lots of unnecessary emails notifing
everyone on issuezillas notifier list for each issue.
Kind regards,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
