Dear All, by looking at the new tickets inserted in the backlog, as well as checking the updates to those already created in the past, I found that there are still cases in which new errors are introduced in the descriptions, i.e. the rules are not applied as they should. This is shown also by the weekly checks by Manuel (backlog excel files): while it can be noticed that many old errors are removed thanks to your commitment, new errors are unfortunately introduced so that the final situation doesn't improve as expected. You can derive most of the rules to apply by checking the excel sheets distributed to you in the past days (usually, at the beginning of each tab there is an explanation of the kind of error found), however I report below a few rules that deal with the most common source of errors found in the backlog. I invite you all to check the tickets you have created/updated against such rules, and update again them, thanks. - Epics o ReleaseID: Not required o SprintID: Not required o States: Open, Under execution (there must be at least one related Feature Under execution, otherwise the Epic cannot be considered Under execution), Closed - Features o ReleaseID: Mandatory o SprintID: Not required o Most important States: Open, Scheduled (when ReleaseID is assigned, but it is not yet the current one), Under execution (only if ReleaseID corresponds to current minor Release), Under Verification, Closed - Story, WorkItem o ReleaseID: Mandatory o SprintID: Mandatory o Most important States: Open, Scheduled (when SprintID is assigned, but it is not yet the current one), Under execution (only if SprintID corresponds to current one), Under Verification (e.g. when a review from somebody else is expected), Closed - Common to Feature, Story, Workitem o If they are assigned to a past ReleaseID and/or SprintID , they cannot be in Open or Under execution state. Currently we are in ReleaseID=3.2 and SprintID=3.2.1. There cannot be tickets with older Release or Sprint ID and still in Open or under execution state o If you have such kind of tickets, then: § If Open, reassign to a later ReleaseID/SprintID (according to the rules above which differentiate Features from Stories/WorkItems) and put in 'Scheduled' state § If Under Execution, reassign to current ReleaseID/SprintID if the activity is not complete, or close if the activity is finished Hope this helps in converging more rapidly. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20131018/2ded09ef/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20131018/2ded09ef/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy