Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
40
-
Description
Hi everyone,
Thank you for your feedback. We appreciate your input and understand the importance of addressing our users' suggestions. Unfortunately, we don't have plans to address this specific suggestion in the next 12 months.
However, I want to assure you that your feedback is valuable to us. Over the last 12 months we have successfully implemented many highly voted suggestions including code-owners, resolvable comments and auto-merge and our upcoming roadmap includes a number of other top voted suggestions including dark theme, draft pull requests and multi-line comments. For the most up-to-date information on what features are coming soon please visit our roadmap.
Once again, thank you for sharing your thoughts with us. Your feedback plays a crucial role in shaping the future of our product. We do continually review these priorities and will continue to do so over the coming year to determine when and how we might be able to address this idea. You can learn more about our prioritization process here.
Cheers,
Sarah Bolt
Product Manager - Bitbucket 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
-
-
- Closed
- causes
-
PS-62163 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-
