Open byt3sage opened 1 year ago
@plittlewood-rpt pretty please could I have some sort of timeframe on this? :)
Due to the current roadmap there is no immediate plan to start looking at this. The reason these filters aren't available is due to the underlying data structure. Without altering how this data is stored (or duplicating it to a more suitable data store) adding these filters would cause the APIs to timeout.
@plittlewood-rpt https://github.com/reapit/foundations/issues/10024
Sorry just a tad confused - here you said it might be doable for location - are you saying none of it is doable now due to the underlying data structure?
Hi @jaetoole sorry it's been waiting for me to log a separate ticket for location filtering which I've now done and we'll refine this week. Thanks
Logged internal ticket PBI-5299 to look at refactoring of applicant position/status/buying reason data storage
@HollyJoyPhillips we can't see the state of the internal ticket so could you provide us an update please?
Hi @byt3sage, I've requested an update from the relevant department. Thanks.
Just a heads up, I'm leaving the business soon so any correspondance for this should be passed to @BradStrutt and @rlockett1121
Is your feature request related to a problem? Please describe. It's impossible to search for an applicant by area, by buying reason, by status or by position which are all the main things you'd want to search for applicants on really!
Describe the solution you'd like Just to expose these fields so we can request applicants by filtering them.
Describe alternatives you've considered Happy to hear any but the only solution is to load all of our applicants and filter them out manually which is going to screw us on request count.
Specification