Hi David, Moving the requirements is not a big deal as there is currently very little there for Frankfurt as most requirements are captured via the use case/fn/non-fn work. Its re-establishing the filters etc for this view to function is where I see some thought/consideration is reuired: https://wiki.onap.org/display/DW/ONAP+Architecture+Release+Requirements .
* EPIQ for a theme * Stories for the requirements. (note, the frankfurt one is still needs some cleaning up from my part). BR, Steve From: David McBride <[email protected]> Sent: Thursday, 22 August 2019 23:12 To: Stephen Terrill <[email protected]> Cc: [email protected]; Scott Blandford <[email protected]>; Alla Goldner <[email protected]>; [email protected] Subject: Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements Hi Steve, My intent was to begin doing that for the Frankfurt release; however, I'm aware that it can take some time to turn a big ship. How difficult would it be to put those requirements into REQ? David On Thu, Aug 22, 2019 at 12:34 PM Stephen Terrill <[email protected]<mailto:[email protected]>> wrote: Hi David, I think it’s a good idea as an ambition, For which release were you thinking that this should be applied. I ask as in the Architecture sub-committee we have been capturing the architecture lead requirements (which are not too many but some) in that JIRA project currently, and have a link to that from the release requirement list, and that is they way I have requested for Frankfurt as well. BR, Steve From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of David McBride via Lists.Onap.Org<https://protect2.fireeye.com/url?k=169c4687-4a15e94e-169c061c-0cc47ad93e1c-5cbfcf7c32142fd3&q=1&u=http%3A%2F%2Flists.onap.org%2F> Sent: Thursday, 22 August 2019 19:54 To: Scott Blandford <[email protected]<mailto:[email protected]>> Cc: Alla Goldner <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] [Onap-usecasesub] JIRA entries for use cases and functional requirements Team, I didn't realize that Alla was going to send that mail. I've been working on a process for documenting requirements in JIRA. I was going to roll it out a little later, but since Alla pushed the issue, let's go with it. Overview: * I setup a new JIRA project called "Release Requirements (REQ)", where I expect all requirements issues to be created. * I created a template for new release requirements from which I expect all requirements JIRA issues to be cloned (REQ-1<https://protect2.fireeye.com/url?k=9d201a62-c1a9c04e-9d205af9-0cc47ad93da2-0790e4b654a5fb5b&q=1&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FREQ-1>). * I drafted some instructions<https://protect2.fireeye.com/url?k=66dac34b-3a531967-66da83d0-0cc47ad93da2-f60c5df44638832b&q=1&u=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FDocumenting%2BRelease%2BRequirements%2Bin%2BJIRA> for creating new requirements issues. I still have some things to figure out around workflow, but I think that we have enough to get started. I'd be interested in your feedback on this proposal. David On Thu, Aug 22, 2019 at 10:03 AM Scott Blandford <[email protected]<mailto:[email protected]>> wrote: Alla, Under which project should the Use Case JIRAs be registered? Scott Blandford From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Alla Goldner Sent: Thursday, August 22, 2019 11:25 AM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [Onap-usecasesub] JIRA entries for use cases and functional requirements Resending – got error message of “undeliverable mail” From: Alla Goldner Sent: Thursday, August 22, 2019 6:06 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: JIRA entries for use cases and functional requirements Hi all, It was communicated during today’s TSC call that documenting all use cases and associated requirements should be done in JIRA, starting from Frankfurt Release.. The idea is to be able to replace the release requirements tables in the wiki with a JIRA dashboard, so it would be easier and shorten processes for PTLs. Requirements owners – please document your newly proposed requirements for Frankfurt in JIRA ASAP, as presence/lack of the requirement fulfillment may become one of prioritization criteria. Best Regards, Alla This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=nXZ_DJwWAJPGxDWsh7AkqQ&m=ykncg6D4or1Lm7El3WlDMTbFNQa7hQsAuldPd7dnzaw&s=cmUEbr-saN3l4ub6hBYWYS0nggVmWagJ20KV6Jh1iP4&e=> -- David McBride Release Manager, OPNFV Mobile: +1.805.276.8018<tel:%2B1.805.276.8018> Email/Google Talk: [email protected]<mailto:[email protected]> Skype: davidjmcbride1 IRC: dmcbride -- David McBride Release Manager, OPNFV Mobile: +1.805.276.8018<tel:%2B1.805.276.8018> Email/Google Talk: [email protected]<mailto:[email protected]> Skype: davidjmcbride1 IRC: dmcbride -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5377): https://lists.onap.org/g/onap-tsc/message/5377 Mute This Topic: https://lists.onap.org/mt/32991994/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
