[$100] Filter "pills" should not pull form a static file.

[wdprice]

The "pills" near filters should pull directly from a database, not from a flat file outlining the options.

Example of current state:

The locations listed are defined in: https://github.com/topcoder-platform/u-bahn-app/blob/develop/client/src/services/static-data.js

Future State:
Default pill values should be determined by values that exist in the database for the current organization.
Same behavior should apply for Achievements.

[wdprice]

@cwdcwd - Another option here is could allow orgs to define the default pill values per org then look up the rest. This would be useful for cutsomers which a number of set offices (like a certain finserv company who has Zurich, Barcelona, Japan, etc.).

[callmekatootie]

@wdprice Do we need to carry this out for Achievements too?

[wdprice]

@callmekatootie Yes

[callmekatootie]

Expected:

• Currently, on page load, after selecting org, we get the list of attributes located in that org (see the network requests made after org selection)
• In this list, there will be an attribute with name "location" - case sensitive. Read it off the REACT_APP_ATTRIBUTE_ID_LOCATION environment variable which will have the value of location.
• Note the id of this attribute - DO NOT hardcode the attribute id, as it is different for different orgs.
• Now, check out Manage Filters tab. When user activates any custom attribute filter, it appears in the sidebar. User can then search for values, which results in network requests based on the value entered. Make a note of the api call being made, and the values passed to it, which includes the attribute id.

Now, for this ticket, we are expecting the following changes:

• For the Location filter, we currently get the values statically. Delete the static values (and any associated code).
• Next, you will use the attribute id for "location" attribute, and just like the filter for the custom attributes, for location, the filter will be a suggestion box where user can type values and they will get suggestions
• For this, you need to use the same api call as the one for the custom attributes but you will be passing the attribute id of location here instead to get the values for location.

Rest of the workflow will be the same - user will get suggestions in the dropdown (or no results found message when no results are available) and user can select a value from the suggestion which will then trigger the search based on the selected location. User can reset the filter as well as remove individual selected filter pills.

IMPORTANT - Solution expected in 12 hours after you pick. DO NOT pick if you cannot provide solution within this time.

[callmekatootie]

Also note - ticket talks about Achievements too. But for now, ignore it.