Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
289
-
Description
Hi everyone,
Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Data Center.
We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.
I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
Cheers,
Imran Khan
Product Manager - Bitbucket Server and Data Center
The code search shipped with 4.6.0 does not handle punctuation well when indexing code. In order to locate occurrences reliably, it should be improved to allow for search criteria with certain punctuation characters taken into account.
Comments with example searches and example results are very welcome to help us cover the right set of characters.
As a workaround it is possible to search for adjacent strings (> 2 characters each) separated by punctuation using phrase syntax. eg to find left_pad you could search for "left pad" (including quotes).
Original description:
Hi,
we have installed the version 4.6.0 of the bitbucket server and will replace the stash soon.
In the document:
https://confluence.atlassian.com/bitbucketserver/search-for-code-in-bitbucket-server-814204781.html
the options and restrictions of the code search are documented.
In our company we have a lot of projects and repositories which means that there is a need to find code for global refactorings in a very exact way that result in a small amount of matches.
Because of that need, the following restrictions are not good for the results we get:
- All punctuation characters are removed
- Case is not preserve
- Regular expressions in queries are not supported
Is there a plan to improve the query posibilities in the next releases?
One small improvement might help to minimize matches. If we get a filename: key word beside the ext: key word to restrict our search.
Is there already such a key word?
Regards
Harald
Attachments
Issue Links
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
BSERV-14265 search can't find matches when searched for exact matches for keywords in condition where there’s a string in camelCase in between hyphens
-
- Gathering Impact
-
- causes
-
PS-62163 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-
