Re: [openstack-dev] [all] What's new in StoryBoard?

On 2017-02-20 01:06:22 -0500 (-0500), Kevin Benton wrote: > Thanks for the pointers. > > So the plan for the projects with a lot of cross bug reports then is to > wait until a unified switch then? Right. While our spec[*] predates the cross-project goals model, the idea is that (assuming

Re: [openstack-dev] [all] What's new in StoryBoard?

Thanks for the pointers. So the plan for the projects with a lot of cross bug reports then is to wait until a unified switch then? On Sun, Feb 19, 2017 at 4:30 PM, Zara Zaimeche wrote: > On 19/02/17 12:19, Jeremy Stanley wrote: > >> On 2017-02-19 03:53:15 -0500

Re: [openstack-dev] [all] What's new in StoryBoard?

On 19/02/17 12:19, Jeremy Stanley wrote: On 2017-02-19 03:53:15 -0500 (-0500), Kevin Benton wrote: If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there some migration tooling to bring stuff from launchpad? It would be nice if we can have all of the existing bugs copied over

Re: [openstack-dev] [all] What's new in StoryBoard?

On 2017-02-19 03:53:15 -0500 (-0500), Kevin Benton wrote: > If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there > some migration tooling to bring stuff from launchpad? It would be nice if > we can have all of the existing bugs copied over so Storyboard would become > the

Re: [openstack-dev] [all] What's new in StoryBoard?

Hi, If an existing project (e.g. Neutron) wants to adopt StoryBoard, is there some migration tooling to bring stuff from launchpad? It would be nice if we can have all of the existing bugs copied over so Storyboard would become the single source of truth rather than a mix between both storyboard

[openstack-dev] [all] What's new in StoryBoard?

Hello All! In your continued education about our new task tracking tool, we have a new blog post! It's focus is on the new functionalities that Storyboard provides [1]. We hope that all of these posts are helping you get more comfortable with the tool. If you missed any of our previous