-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search by more than one criteria of same type #7225
Comments
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Not Stale |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Not stale |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
+1 |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Not stale |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Query - Can multiple search criteria verbiage be entered in the asset search bar? Does the search bar follow specific boolean search methods? |
I don't think so |
The search query splits on commas and spaces and searches each word. Saw
it recently in the code.
…On Wed, Mar 4, 2020 at 1:31 AM ajsy ***@***.***> wrote:
I don't think so
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7225?email_source=notifications&email_token=AB6X6MFTDTV3YYQGCUQX573RFXYV5A5CNFSM4H5FYBE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENWRJKY#issuecomment-594351275>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6X6MDC6LP274CM7IJKMTDRFXYV5ANCNFSM4H5FYBEQ>
.
|
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This is still relevant. |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still relevant |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes it is still relevant.
Cliff Van Buggenhout
… On 2 Sep 2020, at 08:10, stale[bot] ***@***.***> wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#7225 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMWOXXU5CBJWNPGREQAEGETSDXOWDANCNFSM4H5FYBEQ>.
|
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Yes. Still relevant.
From: stale[bot] <[email protected]>
Sent: Friday, December 25, 2020 12:23 PM
To: snipe/snipe-it <[email protected]>
Cc: Discovery Learning Center Labs (Engineering Hall) <[email protected]>; Comment <[email protected]>
Subject: Re: [snipe/snipe-it] Search by more than one criteria of same type (#7225)
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_snipe_snipe-2Dit_issues_7225-23issuecomment-2D751279334&d=DwMCaQ&c=S1d2Gs1Y1NQV8Lx35_Qi5FnTH2uYWyh_OhOS94IqYCo&r=uHOq-KXgG8aoh7V9y5QJ3mV01PlNGHDTV5Nl8T24Bs8&m=KoPrUG0gtbLX10EzYblWljQd0r48miYO6TvB__puWGw&s=nLLiGQ0vJKmKVuqJ7iTGfn5IApGtKjTzNeNwyjhvyr0&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADJFRGYVTRQJICAZ6DJRTKDSWTKBLANCNFSM4H5FYBEQ&d=DwMCaQ&c=S1d2Gs1Y1NQV8Lx35_Qi5FnTH2uYWyh_OhOS94IqYCo&r=uHOq-KXgG8aoh7V9y5QJ3mV01PlNGHDTV5Nl8T24Bs8&m=KoPrUG0gtbLX10EzYblWljQd0r48miYO6TvB__puWGw&s=hHLRG1AfOqr8EXx3mOqlD9h_UEnv_UCu9NA22r0n2mk&e=>.
|
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Would be great if the search would support simple AND, OR and EXCLUDE parameters. So I could search for stuff...
Maybe using chars like &, | and - as parameters... |
Any news about this nice feature? |
@snipe - Sorry to tag you on this mate, but this has been here for over a year without any official comment. Thank you! |
No insight to offer at this time. We're really heads down on v6 and SCIM right now. Many tickets have been here for over a year. Doesn't mean we won't get to them, just means other stuff has been higher priority. |
Thank you for answering, even if the team aren't prioritizing it, it's good to know what's the current status of things. If you have any workaround for the search functionality or at the very least provide some clarity on how can we search for more than a single term. that would be really really helpful! (consider companies with 200+ computers on different locations, and you need to search for undeployed model in specific location to know what needs restock for example. this is kinda important for an inventory app. Thanks again! |
@avielic - You can already search by location_id and status label type at the same time via API, or by drilling down into the location or status label listings and searching on the other via GUI. |
@snipe sorry for the late reply. On another note, on 5.4.1 (probably before that too) the search in the assests, doesn't catch previous owners (e.g. history) |
It's still on the list, it's just very difficult to execute well.
I'm not sure if it was ever supposed to do that, but if so, it should be in a new bug. |
I'll try to find time to submit one tomorrow. today was a long day |
Hi, so when I want to search something through an API, for example
This is still not possible and my only 2 options are if I'm right: Option 1 - make more API calls, then do an intersection
Option 2 - make 1 API call, then filter on server-side
Is this correct? |
Server (please complete the following information):
Is your feature request related to a problem? Please describe.
I am unable to search through assets by multiple criteria of the same type. For example: I have some equipment in locations 1-19 and 1-16. I am unable to search for all the assets that are in 1-16 and 1-19 at the same time, I need to do two searches at once. Hence, I also need to do two exports also.
Describe the solution you'd like
The simplest solution would be to use some kind of symbol to separate two or more values to search by. So if I want all assets that are either in 1-16 or 1-19 to show up, I'd just separate them with ';' in the search field.
Describe alternatives you've considered
The usage of quotation marks could also be added to be sure that whatever symbol is used as separation can also be used in a search if it is a part of an asset name, location, etc.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: