+1 Thanks, Shankar.
On Thu, Jul 12, 2018 at 12:43 PM Pamela Dragosh <pdrag...@research.att.com> wrote: > +1 > > > > Pam Dragosh > > ONAP Policy PTL > > > > *From: *<onap-rele...@lists.onap.org> on behalf of "MAHER, RANDA" < > rx1...@att.com> > *Date: *Monday, July 9, 2018 at 9:46 AM > *To: *"onap-rele...@lists.onap.org" <onap-rele...@lists.onap.org> > *Cc: *onap-tsc <onap-...@lists.onap.org>, "onap-discuss@lists.onap.org" < > onap-discuss@lists.onap.org> > *Subject: *Re: [Onap-release] [ptl][jira] Propose alignment on 1 Jira > workflow > > > > ****Security Advisory:* This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > > Hello everyone, > > > > This topic was discussed on today’s PTL call. I am resending email so you > don’t have to dig for it. > > Please provide your feedback if you’re in agreement or if you have any > questions. > > The goal is to align on a single workflow in ONAP. > > > > Also, another topic raised during PTL call, but not part of the attached > proposal, but I wanted to note it here: > > · We should align on the set of Jira issue types that will be > used across the projects to ensure issues don’t fall through the cracks. > > · Today, most projects use: Epics, Stories (& sub-tasks available > within story), Tasks, Bugs > > · There are some projects that also use New Feature > > · What is the set we want to support for ONAP projects? > > > > Thanks, Randa > > > > *From:* onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] *On > Behalf Of *MAHER, RANDA > *Sent:* Monday, June 25, 2018 9:30 PM > *To:* onap-rele...@lists.onap.org > *Cc:* onap-tsc <onap-...@lists.onap.org>; onap-discuss@lists.onap.org > *Subject:* [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow > > > > ****Security Advisory:* This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > Greetings PTLs, > > > > One of the items in the Beijing Retrospective was confusion over the two > separate Jira workflows in play today. > > I would like to submit the following for consideration to align on ONE > Jira workflow. This is low hanging fruit and an easy enough change to > implement to progress on addressing one of the concerns raised during > Lesson’s Learned discussions. > > > > I believe the attached workflow is flexible enough to handle the > uniqueness of ONAP as well as not introduce overhead for teams. > > > > Please review attached slides and provide your +1 if you agree to the > proposal. > > > > Thanks, > > Randa > > APPC PTL > > > > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11097): https://lists.onap.org/g/onap-discuss/message/11097 Mute This Topic: https://lists.onap.org/mt/23290003/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
