Facing a issue with filtering tickets

Tejasri_Kalluri · May 28, 2021, 6:28am

Hi Team,

One of the client account enable fields for filtering tickets when ticket fields have values result coming as zero

This is a screenshot of the ticket:

My ways:

here encode single quotation not displaying properly I worked on that one also instead of single quotation used %27

Let me know anything I missed here?

Thanks,
Tejasri

yusrakhatri · May 28, 2021, 7:03am

Hello Tejasri,

Your last two requests:

they look absolutely fine and they should give you the desired result.

However, on reading the documentation, I noticed this, quoting it here:

If you’re not getting a result for the above query, there’s a chance that the field might have been created recently or it has been moved to a new infrastructure. To query on these custom fields, use ‘custom_string’ instead of the actual field label.

Let me know if this works for you.

Tejasri_Kalluri · May 30, 2021, 4:31pm

@yusrakhatri, If another ticket for another custom field(other than I am looking) also has the same value then we won’t get actual results right?

ManiDeepak_Vandrangi · May 31, 2021, 4:06am

Can you please try /api/v2/search/tickets?query="(cf_id_number:7894)" in postman or /api/v2/search/tickets?query=%22(cf_id_number:7894)%22 in cURL.

Tejasri_Kalluri · May 31, 2021, 6:59am

Hey @ManiDeepak_Vandrangi,
Tried about 2 queries still results are showing zero

ManiDeepak_Vandrangi · May 31, 2021, 7:18am

I have a ( and ) around " " in query as shown in example. Even if you are facing the error, please DM me as we need to get that customer account details.

ManiDeepak_Vandrangi · May 31, 2021, 8:30am

We checked the account and found the custom fields are not of type numbers but of type “Single Line Text”

kaustavdm · May 31, 2021, 8:44am

Interesting. I was testing the API for edge cases, just in case. So if these custom fields are “Single Line Text”, wrapping the value with single quotes should work in this case, right? Like:

/api/v2/search/tickets?query="cf_id_number:'7894'"

Tejasri_Kalluri · May 31, 2021, 9:14am

@ManiDeepak_Vandrangi, I tried with single quotes even results are showing zero

ManiDeepak_Vandrangi · May 31, 2021, 9:25am

@Tejasri_Kalluri
Can you try with query=“custom_string:‘7894’” as @yusrakhatri suggested ? Replace 7894 with whatever values you want to search for.

Tejasri_Kalluri · May 31, 2021, 10:01am

Yes @ManiDeepak_Vandrangi, I tried the results are coming. but also I found a drawback in this query. If another ticket, another custom field(other than id number and policy number fields) also has the same value(7894) then we won’t get actual id number or policy number filter tickets right?

ManiDeepak_Vandrangi · May 31, 2021, 10:04am

Yeah @Tejasri_Kalluri. We are checking with team to see if there are any alternatives

Tejasri_Kalluri · May 31, 2021, 10:05am

okay thank you @ManiDeepak_Vandrangi

Omar_Atta · August 10, 2022, 4:05pm

Did you find any solution to this issue?