Hi Ghada! I really like what you're doing here, and want to combine it with the sub-project approach I had already started. There is a bit of over-lap between the two but I think we can work it out. For instance I'm thinking that a bug in Documentation might be marked as "[Bug] [Doc]", and so on. Basically each story gets marked with a kind for what kind of thing it is, and what sub-project it's part of. I have built both worklists and boards for testing and experimentation, and there are some usability issues with them. Both are access controlled and can only be modified by the owner granting explicit permission. This might be fine for things we want to control closely but not so much otherwise. Manually populating worklists is painful given the number of stories we already have. Populating them with automated queries works well but automated worklists can't be sorted the way manual lists can be. I started out using Etherpads and Ethercalc tables since those can be sorted, but we are hitting basic data integrity issues with Ethercalc that are really starting to scare us. I've put this on the agenda for our call tomorrow but we might want to hold a separate call with a smaller audience. brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Tuesday, July 17, 2018 7:19 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches As discussed in last Wednesday's meeting, I have updated the StarlingX wiki with the tracking proposal below: https://wiki.openstack.org/wiki/StarlingX#Meetings I've also added a [Test] prefix for test-related work items. I have updated all stories with prefixes. If I mislabeled something, please feel free to fix as you see fit. Regards, Ghada -----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 [Help] Request for assistance / help ** 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