Hey Tony :) So I think the best way to deal with it would to disable bug reporting for requirements in LP (so nothing new can get filed there and the index won't be discoverable but you can still edit the old bugs) and then to do periodic runs of the migration script to pick up any changes that have happened.
As for dumping SB changes back into LP I don't know that there is a way. Maybe someone else has an idea. Hopefully by updating the description of the reqs project in LP, people will know where to look for the new/current information. Hope that helps! -Kendall (diablo_rojo) On Wed, Jul 11, 2018 at 11:54 PM Tony Breeds <t...@bakeyournoodle.com> wrote: > Hi all, > The requirements team is only a light user of Launchpad and we're > looking at moving to StoryBoard as it looks like for the most part it'll > be a better fit. > > To date the thing that has stopped us doing this is the handling of > bugs/stories that are shared between LP and SB. > > Assume that requirements had migrated to SB, how would be deal with bugs > like: https://bugs.launchpad.net/openstack-requirements/+bug/1753969 > > Is there a, supportable, bi-directional path between SB and LP? > > I suspect the answer is No. I imagine if we only wanted to get > updates from LP reflected in our SB story we could just leave the > bug tracker open on LP and run the migration tool "often". > > Yours Tony. > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
