[Fiware-qualityassurance] FW: [FIWARE] Name of jira tickets

Fernando López fernando.lopez at fiware.org
Thu Mar 16 13:26:20 CET 2017


Dear Clara et all.

This is the list of tickets that should be changed, all the tickets have 
assignee "Andrea La Porta":

https://jira.fiware.org/browse/APP-1087

https://jira.fiware.org/browse/APP-1097

https://jira.fiware.org/browse/APP-1008

Example: https://jira.fiware.org/browse/APP-1088



https://jira.fiware.org/browse/APP-1155

https://jira.fiware.org/browse/DATA-1736

https://jira.fiware.org/browse/DATA-1657

https://jira.fiware.org/browse/DATA-1472

https://jira.fiware.org/browse/DATA-1466

https://jira.fiware.org/browse/DATA-1426

https://jira.fiware.org/browse/DATA-1726

https://jira.fiware.org/browse/MIND-581

https://jira.fiware.org/browse/MIND-619

https://jira.fiware.org/browse/IOT-721

https://jira.fiware.org/browse/IOT-722

https://jira.fiware.org/browse/IOT-715

https://jira.fiware.org/browse/IOT-716

https://jira.fiware.org/browse/IOT-718

https://jira.fiware.org/browse/IOT-720

https://jira.fiware.org/browse/IOT-714


Please try to resolve the problems with the nomenclature of the tickets. 
You can check the status with the backlog tool 
http://backlog.fiware.org/enablers/overview

BR,
Fernando


On 14/03/2017 16:04, Pezuela Robles, Clara M wrote:
>
> Dear all,
>
> It seems some tickets are being generated from QA task are causing 
> naming conflicts in Jira.
>
> Please follow the rules indicated by Fernando below to naming the 
> tickets when created. Correct format is the one marked in yellow
>
> Thanks
>
> Clara Pezuela
>
> Head of IT Market
>
> Research and Innovation Group
>
> ARI booklet 
> <https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf>
>
> Atos Spain SA
>
> Clara.pezuela at atos.net <mailto:Clara.pezuela at atos.net>
>
> +34 675 62 9974
>
> Atos_Olympic_Games_Logo_signature
>
> *From:*Fernando López [mailto:fernando.lopez at fiware.org]
> *Sent:* Tuesday, March 14, 2017 3:31 PM
> *To:* Pezuela Robles, Clara M
> *Subject:* [FIWARE] Name of jira tickets
>
> Hola Clara,
>
> Estoy observando que en la creación de los tickets de QA asociados a 
> los GE se está cometiendo un fallo en la nomenclatura de los tickets.
>
> Por ejemplo este ticket:
>
> https://jira.fiware.org/browse/DATA-1472
>
> Tiene el siguiente summary:
>
> FIWARE.Bug.QA.API.DataContext.StreamOriented-Kurento - Bad Request
>
>
> Esto produce un error, porque no está especificado correctamente el 
> chapter y el componente. El formato de los tickets debería ser:
>
> FIWARE.Bug.<Chapter>.<GE>.<lo que sea>
>
> Donde:
> - Chapter puede ser
>
>     Apps, Cloud, Data, I2ND, IoT, Security, WebUI, Ops, Academy, 
> Catalogue
>
> - GE puede ser:
>
>     Apps: ApplicationMashup, BusinessAPIEcosystem, Marketplace, 
> Repository, RSS, DataViz-SpagoBI, ApplicationMashup, Store, 
> BusinessAPIEcosystem.
>     Cloud: CloudPortal, ResMgmt, Monitoring, ObjectStorage, 
> PaaSManager, PolicyMgr, SwDeployConfig, Murano, Docker.
>     Data: CEP, CKAN, BigData-Analysis, Stream-oriented, 
> OrionContextBroker, AeonCloudMessaging, 
> MetaDataStoreManagementPlatform, SocialDataAggregator, 
> SocialSemanticEnricher.
>     I2ND: Kiara, OFNIC, Netfloc, Robotics
>     IoT: EPCGE, DataEdge-Cepheus, IDAS, BackendIoTBroker, IoTDiscovery
>     Security: AuthorizationPDP, CyberSecurity, IDM-KeyRock, PEP-Proxy, 
> Privacy, TrustworthyFactory
>     WebUI: AugmentedReality, CloudRendering, Fives, GISDataProvider, 
> InterfaceDesigner, POIDataProvider, RealVirtualInteraction, 
> Synchronization, VirtualCharacters, WebTundra3D, XML3D, 2D-3DCapture, 
> 2D-UI
>     Ops: Dash, Deploy, Health, Toolkit
>     Academy: Builder, Platform, Player
>     Catalogue: Platform
>
> Please, explica el tema a la gente porque está ocasionando errores en 
> el backlog en los distintos chapters.
>
> BR, Fernando
>
> -- 
>
> *−−−
> Fernando López *
>
> 	
>
> 	
>
> *FIWARE Cloud and Platform Senior Expert
> FIWARE Foundation *
>
> 	
> 	
>
> FIWARE Foundation
>
> Franklinstrasse 13A
> 10587 Berlin
>
> 	
> 	
>
> email: fernando.lopez at fiware.org <mailto:fernando.lopez at fiware.org>
> www: http://fiware.org
> twitter: @flopezaguilar @FIWARE
> skype: fernandola
>
> 	
> 	
>
> This e-mail and the documents attached are confidential and intended 
> solely for the addressee; it may also be privileged. If you receive 
> this e-mail in error, please notify the sender immediately and destroy 
> it.
> As its integrity cannot be secured on the Internet, the Atos group 
> liability cannot be triggered for the message content. Although the 
> sender endeavors to maintain a computer virus-free network, the sender 
> does not warrant that this transmission is virus-free and will not be 
> liable for any damages resulting from any virus transmitted.
>
> Este mensaje y los ficheros adjuntos pueden contener información 
> confidencial destinada solamente a la(s) persona(s) mencionadas 
> anteriormente y pueden estar protegidos por secreto profesional.
> Si usted recibe este correo electrónico por error, gracias por 
> informar inmediatamente al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos 
> no se hace responsable por su contenido. Su contenido no constituye 
> ningún compromiso para el grupo Atos, salvo ratificación escrita por 
> ambas partes.
> Aunque se esfuerza al máximo por mantener su red libre de virus, el 
> emisor no puede garantizar nada al respecto y no será responsable de 
> cualesquiera daños que puedan resultar de una transmisión de virus. 

-- 
−−−
Fernando López 	
	
FIWARE Cloud and Platform Senior Expert
FIWARE Foundation 	
	FIWARE Foundation
Franklinstrasse 13A
10587 Berlin
email: fernando.lopez at fiware.org <mailto:fernando.lopez at fiware.org>
www: http://fiware.org
twitter: @flopezaguilar @FIWARE
skype: fernandola 	
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20170316/1f885bc7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11614 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20170316/1f885bc7/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 251283 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20170316/1f885bc7/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Foundation-31B.png
Type: image/png
Size: 251283 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20170316/1f885bc7/attachment-0005.png>


More information about the Fiware-qualityassurance mailing list

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