Add ability to tag/label repositories for searching/filtering/automatic board building?
Problem to solve
Once the number of repositories grows beyond a certain amount, it becomes nearly impossible to perform operations on groups of projects unless the projects are added to specific "groups" or "subgroups". The problem with groups and subgroups is two-fold:
1) They are singular... a repo can only be a member of a single group or subgroup
2) They are very fixed... we dont necessarily want or need to physically move a project to another group, we really only have a need to "re-label" it so that it can be found when filtering on a specific label/tag.
Intended users
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Presley (Product Designer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Dana (Data Analyst)
Further details
Proposal
Add labeling features currently used on issues to repos (sounds simple, but obviously there are complications/additions/separations that need to be accounted for.
Permissions and Security
Should follow standard security restrictions already in place for UI/API
Documentation
None
Testing
None
What does success look like, and how can we measure that?
Ability to (through both the UI and the API) return a list of projects that meet a list (one or more) of specified labels. Complex AND/OR logic would be appreciated but not necessary for a first iteration.
What is the type of buyer?
Core