Hi,

I'm looking for advice on the best way to organise bugs for our team. We work on the Files app on ChromeOS.

We currently have the following components for FileManager:

Platform>Apps>FileManager
Platform>Apps>FileManager>Drive
Platform>Apps>FileManager>CloudImport

However, we are not using these any more. Instead, all bugs have the component Platform>Apps>FileManager, and we use a labelling system for sub-components (documented at go/xf-triage). We have two sets of labels:

1. CrOSFilesFeature-* (CrOSFilesFeature-Zip, CrOSFilesFeature-QuickView, CrOSFilesFeature-FileIntents, CrOSFilesFeature-DriveSync, CrOSFilesFeature-TeamDrives, CrOSFilesFeature-FileSystemProvider, CrOSFilesFeature-CloudImport, CrOSFilesFeature-LowStorage, CrOSFilesFeature-ARC, CrOSFilesFeature-ExternalMedia, CrOSFilesFeature-Crostini and CrOSFilesFeature-NavRefresh), which is which feature the bug applies to

2. CrOSFilesCategory-* (CrOSFilesCategory-Touch, CrOSFilesCategory-CodeHealth, CrOSFilesCategory-Testing, CrOSFilesCategory-Accessibility, CrOSFilesCategory-UMA, CrOSFilesCategory-UI, CrOSFilesCategory-Performance and CrOSFilesCategory-Offline), which labels the type of work the bug requires

Each bug gets at most one of each label. We use both of these in our triage process to organise the large backlog of bugs we have for the file manager. Right now we have to type the label names perfectly, but it would be much easier and less error-prone if we had autocompletion for them. However, I'm aware you may not want to add these labels since they don't match anything else in Chrome.

Do other teams have labelling systems like this? How do they manage their bugs? I'm not sure if a component makes sense, since we frequently add/remove features from the Files app and would need to update these labels at least once a month. And is there an existing system for the Category labels?

Any advice on the best way to organise these bugs, or how other teams do things, would be appreciated.

Thanks!