[Fiware-chapter-architects] Deliverables: Lab Support Report

Alex Glikson GLIKSON at il.ibm.com
Wed Jul 22 22:27:08 CEST 2015


> It cannot be done automatically because there?s not a way to do it. You 
know they are issues coming from external users.
> A small part could be done automatically in the pattern, if the channel 
were properly assigned but never completely since the summary needs to be 
made meaningful by the GE owner. 
> And when doing it he can copy & paste FIWARE.Request.Lab in the summary.

How about keeping the ticket subject as is, and programmatically adding a 
prefix comprising chapter and component?

Thanks for elaborating on the rest of the details!

Regards,
Alex

====================================================================================
Alex Glikson
Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab; FIWARE 
Cloud Leader & Architect
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: 
+972-54-6466667 | Fax: +972-4-8296112





From:   MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com>
To:     Alex Glikson/Haifa/IBM at IBMIL
Cc:     "fiware-chapter-architects at lists.fiware.org" 
<fiware-chapter-architects at lists.fiware.org>, 
"fiware-chapter-leaders at lists.fiware.org" 
<fiware-chapter-leaders at lists.fiware.org>, MIGUEL CARRILLO PACHECO 
<miguel.carrillopacheco at telefonica.com>
Date:   22/07/2015 06:44 PM
Subject:        RE: [Fiware-chapter-architects] Deliverables: Lab Support 
Report



It cannot be done automatically because there?s not a way to do it. You 
know they are issues coming from external users.
A small part could be done automatically in the pattern, if the channel 
were properly assigned but never completely since the summary needs to be 
made meaningful by the GE owner. 
And when doing it he can copy & paste FIWARE.Request.Lab in the summary.
 
Well, the backlog hierarchy also includes a work item (COR-380) for me to 
program the script that creates the deliverables from the input available 
in JIRA. 
 
If you read the issue for delivery, in cloud case, COR-382, it describes 
the steps to take:

 
These issues are also assigned to me so as to produce and deliver the 
deliverables. 
Then, the pattern is very similar to the backlog deliverable
 
And what content?
They?ll have:
1 ? Enabler Identification
                2 ? Graphs to provide a summary view of content and 
reaction times
                3 ? List of help desks request solved in the enabler. 
 
I hope it can be understood now.
 
Kind regards,
Manuel
 
 
From: Alex Glikson [mailto:GLIKSON at il.ibm.com] 
Sent: miércoles, 22 de julio de 2015 17:18
To: MANUEL ESCRICHE VICENTE
Cc: fiware-chapter-architects at lists.fiware.org; 
fiware-chapter-leaders at lists.fiware.org; MIGUEL CARRILLO PACHECO
Subject: RE: [Fiware-chapter-architects] Deliverables: Lab Support Report
 
I did look at the various JIRA tickets, and the only 'hint' I've found is 
that we need to rename all the helpdesk tickets according to the new 
convention (too bad... why couldn't we do it automatically in the first 
place, when tickets are created?), plus a link to the general description 
of the helpdesk backlog. 
What I didn't understand is what exactly the deliverable will include, who 
will produce it, and whether anything else besides renaming all the 
tickets is needed. 

Thanks, 
Alex 





From:        MANUEL ESCRICHE VICENTE <
manuel.escrichevicente at telefonica.com> 
To:        Alex Glikson/Haifa/IBM at IBMIL 
Cc:        "fiware-chapter-architects at lists.fiware.org" <
fiware-chapter-architects at lists.fiware.org>, "
fiware-chapter-leaders at lists.fiware.org" <
fiware-chapter-leaders at lists.fiware.org>, MIGUEL CARRILLO PACHECO <
miguel.carrillopacheco at telefonica.com> 
Date:        22/07/2015 05:58 PM 
Subject:        RE: [Fiware-chapter-architects] Deliverables: Lab Support 
Report 




Dear Alex, 
  
I?ve just said that in the email, so I?m not sure you haven?t read it or 
how to understand your email. 
  
Manuel 
  
From: Alex Glikson [mailto:GLIKSON at il.ibm.com] 
Sent: miércoles, 22 de julio de 2015 16:54
To: MANUEL ESCRICHE VICENTE
Cc: fiware-chapter-architects at lists.fiware.org; 
fiware-chapter-leaders at lists.fiware.org; MIGUEL CARRILLO PACHECO
Subject: Re: [Fiware-chapter-architects] Deliverables: Lab Support Report 
  
Dear Manuel, 

Are there guidelines on how to produce this report? 

Thanks, 
Alex




From:        MANUEL ESCRICHE VICENTE <
manuel.escrichevicente at telefonica.com> 
To:        "fiware-chapter-leaders at lists.fiware.org" <
fiware-chapter-leaders at lists.fiware.org> 
Cc:        "fiware-chapter-architects at lists.fiware.org" <
fiware-chapter-architects at lists.fiware.org> 
Date:        22/07/2015 05:44 PM 
Subject:        [Fiware-chapter-architects] Deliverables: Lab Support 
Report 
Sent by:        fiware-chapter-architects-bounces at lists.fi-ware.org 





Dear Partners, 
 
I?ve just created the backlog for the Lab Support Report Deliverable 
Series. 
You should have received the corresponding notification for the created 
WorkItem, where the activities are described. 
If you had any doubt, please, don?t hesitate to let me know. 
 
http://backlog.fiware.org/delivery/dashboard 
 

 
Kind regards, 
Manuel 
 
---------------------------- 
Manuel Escriche Vicente
Agile Project Manager/Leader 
FI-WARE Initiative
Telefónica Digital 
Parque Tecnológico 
C/ Abraham Zacuto, 10
47151 - Boecillo
Valladolid - Spain
Tfno: +34.91.312.99.72 
Fax: +34.983.36.75.64
http://www.tid.es 
 
 



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, 
puede contener información privilegiada o confidencial y es para uso 
exclusivo de la persona o entidad de destino. Si no es usted. el 
destinatario indicado, queda notificado de que la lectura, utilización, 
divulgación y/o copia sin autorización puede estar prohibida en virtud de 
la legislación vigente. Si ha recibido este mensaje por error, le rogamos 
que nos lo comunique inmediatamente por esta misma vía y proceda a su 
destrucción.

The information contained in this transmission is privileged and 
confidential information intended only for the use of the individual or 
entity named above. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received 
this transmission in error, do not read it. Please immediately reply to 
the sender that you have received this communication in error and then 
delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, 
pode conter informação privilegiada ou confidencial e é para uso exclusivo 
da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário 
indicado, fica notificado de que a leitura, utilização, divulgação e/ou 
cópia sem autorização pode estar proibida em virtude da legislação 
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o 
comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-chapter-architects mailing list
Fiware-chapter-architects at lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-chapter-architects 
 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, 
puede contener información privilegiada o confidencial y es para uso 
exclusivo de la persona o entidad de destino. Si no es usted. el 
destinatario indicado, queda notificado de que la lectura, utilización, 
divulgación y/o copia sin autorización puede estar prohibida en virtud de 
la legislación vigente. Si ha recibido este mensaje por error, le rogamos 
que nos lo comunique inmediatamente por esta misma vía y proceda a su 
destrucción.

The information contained in this transmission is privileged and 
confidential information intended only for the use of the individual or 
entity named above. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received 
this transmission in error, do not read it. Please immediately reply to 
the sender that you have received this communication in error and then 
delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, 
pode conter informação privilegiada ou confidencial e é para uso exclusivo 
da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário 
indicado, fica notificado de que a leitura, utilização, divulgação e/ou 
cópia sem autorização pode estar proibida em virtude da legislação 
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o 
comunique imediatamente por esta mesma via e proceda a sua destruição 


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, 
puede contener información privilegiada o confidencial y es para uso 
exclusivo de la persona o entidad de destino. Si no es usted. el 
destinatario indicado, queda notificado de que la lectura, utilización, 
divulgación y/o copia sin autorización puede estar prohibida en virtud de 
la legislación vigente. Si ha recibido este mensaje por error, le rogamos 
que nos lo comunique inmediatamente por esta misma vía y proceda a su 
destrucción.

The information contained in this transmission is privileged and 
confidential information intended only for the use of the individual or 
entity named above. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received 
this transmission in error, do not read it. Please immediately reply to 
the sender that you have received this communication in error and then 
delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, 
pode conter informação privilegiada ou confidencial e é para uso exclusivo 
da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário 
indicado, fica notificado de que a leitura, utilização, divulgação e/ou 
cópia sem autorização pode estar proibida em virtude da legislação 
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o 
comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150722/217a43f9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5962 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150722/217a43f9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 51993 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150722/217a43f9/attachment.jpe>


More information about the Fiware-chapter-architects mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy