This is a good discussion. If someone can document the Storyboard query interface or point me at the documents, that would be super helpful. Re: worklists, I've tried using them and found that you have to explicitly authorize users to make changes to them. That's not something I want to do a lot of. I'm hoping there's a better way. The nice folks from the Foundation have offered to give us some Storyboard training, so perhaps we should hold off on making any decisions until then. brucej -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Tuesday, July 10, 2018 4:03 PM To: Khalil, Ghada <Ghada.Khalil@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Hi, Storyboard also supports tags, that could be another way to track the stories/issues. Also I would add [help] to the list, this is considering that someone can just create a story to ask a question (similar to the model in Github, where anyone can create issues). -Erich On 7/10/18, 5:25 PM, "Khalil, Ghada" <Ghada.Khalil@windriver.com> wrote: Re-sending due to message formatting issues. My apologies! -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss@lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss