You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, many software forges include issue tracker and wiki in addition to checked out source files. Would it be possible to extend sourcebot to search those as well? It could be pretty useful for projects dealing with large number of issues scattered across many repositories.
Reopening since I think this will involve a separate discussion.
@TwiggyWan yea that is a interesting idea and something we have discussed internally. I'd be interested in learning more about your use case - what code host platform are you using now? Can you not search across all issues within the platform itself?
Reopening since I think this will involve a separate discussion.
@TwiggyWan yea that is a interesting idea and something we have discussed internally. I'd be interested in learning more about your use case - what code host platform are you using now? Can you not search across all issues within the platform itself?
I currently use selfhosted gitlab premium. It is possible to search within all issues of all projects (see https://docs.gitlab.com/user/search/advanced_search/) but as far as I understand it it's purely textual so I cant say get me all issues with substring "foobarbaz" in the description and with label priority=69420.
If I search within a group, I can combine labels and string terms, to somewhat get what I want. But one of the projects I might need to search into has over a thousand issues, so it gets tedious quickly to craft precise enough string + label combination to get down to a manageable of issues to read and find the one i'm actually interested in. Doing this properly seems to be a skill in itself.
So to sum up, having sourcebot help me comb through all this paperwork to help me narrow down the relevant content I need would be very useful.
@TwiggyWan have you tried connecting the GitLab MCP search tool to a coding agent like claude code? Looks like it is able to search issues
I did not know this feature (actually thanks to you I learn about the whole gitlab MCP / gitlab duo!)
However I think that it's a downside that these features are gated behind premium and ultimate subscriptions. So one has to pay gitlab, then pay the language model provider.
Activity
brendan-kellam commentedon Jan 28, 2026
Reopening since I think this will involve a separate discussion.
@TwiggyWan yea that is a interesting idea and something we have discussed internally. I'd be interested in learning more about your use case - what code host platform are you using now? Can you not search across all issues within the platform itself?
TwiggyWan commentedon Jan 30, 2026
I currently use selfhosted gitlab premium. It is possible to search within all issues of all projects (see https://docs.gitlab.com/user/search/advanced_search/) but as far as I understand it it's purely textual so I cant say
get me all issues with substring "foobarbaz" in the description and with label priority=69420.If I search within a group, I can combine labels and string terms, to somewhat get what I want. But one of the projects I might need to search into has over a thousand issues, so it gets tedious quickly to craft precise enough string + label combination to get down to a manageable of issues to read and find the one i'm actually interested in. Doing this properly seems to be a skill in itself.
So to sum up, having sourcebot help me comb through all this paperwork to help me narrow down the relevant content I need would be very useful.
brendan-kellam commentedon Feb 4, 2026
@TwiggyWan have you tried connecting the GitLab MCP search tool to a coding agent like claude code? Looks like it is able to search issues
TwiggyWan commentedon Feb 5, 2026
I did not know this feature (actually thanks to you I learn about the whole gitlab MCP / gitlab duo!)
However I think that it's a downside that these features are gated behind premium and ultimate subscriptions. So one has to pay gitlab, then pay the language model provider.