-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
29
-
Bitbucket Server and Data Center 5.13 included the ability to set up to 5 labels per repo, as suggested in BSERV-2727. This is great, but the user has to go into a repo and click on a label link to see repos with that label.
Here are are some proposals for how this could work.
- Core feature
- Users should be able to use a label: search modifier to perform more fine-grained searches than the label links provide. This would allow searching on files with certain extensions, but only in repos that contain one ore more specified labels.
- Sub-feature 1: Compact syntax
- Further, it would be ideal to have a compact syntax to search through multiple labels, such as label:(prod OR docker) instead of having to use label:prod OR label:docker.
- Sub-feature 2: Wildcard support
- With only five labels available, users may try to combine multiple aspects into a single label, such as prod_docker or prod_selenium, so being able to search for prod_* might be useful for really large repositories. Regular expressions are probably not totally necessary, and would add complexity, so this would be out of scope.
Fellow users, please vote if you'd like to have this, and feel free to suggest modifications to what I've proposed.
- mentioned in
-
Page Failed to load
[BSERV-11079] Support label: modifier in search syntax
+1, we are looking to leverage labels as a workaround for not having subprojects. But not being able to simply list/filter repos in the UI by labels makes it difficult.
I see that the API exists e.g. below will search for all repos that are tagged with "api"
/rest/api/latest/labels/api/labeled?avatarSize=48&type=repository&start=0&limit=25
Jason - Thanks for the link to the REST api endpoints related to labels. I was disappointed to see that you can only create, read, and delete labels though. The primary reason for creating labels (for us, at least) is to query the system to see which projects/repositories have a given label. Without that ability, the feature isn't really useful for our team.
Jeremy, I believe that is actually a plugin rather than a built in feature. The issue for project categories (BSERV-2727) is still open, and just passed it's 10 year anniversary this year.
Dave, there are REST endpoints for interacting with the labels: https://developer.atlassian.com/server/bitbucket/rest/v806/api-group-repository/#api-api-latest-projects-projectkey-repos-repositoryslug-labels-post
Took me a bit to find them; it was easier to find them in the old documentation.
Dave,
There's nothing at the project level, which really limits the usability for us.
I guess projects do have "categories" that you can set under the main /projects/{projectKey}/settings page of your Bitbucket server project. Once set, you can filter the list of projects using the category links shown to the left of the project list, as shown below.
Does that work for you?
Until recently, I didn't even know the labels functionality had been implemented. There's nothing at the project level, which really limits the usability for us. That aside, it looks like a decent set of methods was implemented in the labelService. It's too bad this functionality isn't exposed very well in the user interface (and not at all in the REST api).
We need more then 5 labels in our company. Teams are using labels for automation and we need some labels for reporting. We have exhausted the 5 label limit which is resulting in issues.
+1
This entire concept of "label" seems to be not well thought. How useful it is if one has to go into the repository and scroll to the very bottom of it ( considering a large readme file exists) and then see the labels? It defeats the whole purpose of assigning labels to the repositories if it is not usable.
I would appreciate it if the labels are shown next to the repositories within the project in the list view. This item lists the other important use-cases already very well so I won't repeat them.
+1