914839 - (Jobvite:CustomField) Jobvite: Add Custom Location Field

Status: VERIFIED FIXED

(Websites :: careers.mozilla.org, defect)

Description

[Ben (:bensternthal)]

This bug tracks adding a custom location field for the careers website and instructing jobvite users to use the new field.

Part of this task is to decide the actual values that should be entered. The preliminary list is (note this is not the wording that should actually be used).

Once the final wording is decided please add to this bug for reference.

- A job that needs someone anywhere in the United States.
- A job that needs someone in the Bay Area.
- A job that needs someone in any of our offices world wide, but not remote. 
- A job that allows for remote work
- A job that requires someone to work in Mountain View
- A job that requires someone to work in San Francisco
- A job that requires someone to work in Portland
- A job that requires someone to work in Vancouver
- A job that requires someone to work in Toronto
- A job that requires someone to work in London
- A job that requires someone to work in Berlin
- A job that requires someone to work in Paris
- A job that allows someone to work in any office in Europe
- A job that allows someone to work remote in EU.
- A job that requires someone to work in New Zealand
- A job that requires someone to work in Boston

Comment 1

[Ben (:bensternthal)]

Location mapping is final and accessible here:

https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Apfr2uXG8zVqdFpHZGQxdHNIS0NxVWJDWVJZWmdnUFE#gid=0

Comment 2

[Osmose [:osmose, :mkelly]]

Custom field added to django-jobvite in https://github.com/mozilla/django-jobvite/commit/b1913ad2006aad61c815e5fa4fb40f256bf7cc95.

Is that all for this bug, or does it also cover populating the field?

Comment 3

[Ben (:bensternthal)]

Let's keep this open until we confirm entries have been populated and are correct.

Comment 4

[Mathew Caldwell]

He all.  In talking with the team here, there are a couple additions we need to add to the location filter.  They are:

Bay Area
North America
Europe
Latin America

Comment 5

[Ben (:bensternthal)]

Mkelly - any issues with the additional field items mat mentions above?

Comment 6

[Ben (:bensternthal)]

Adding note for qa, the field name in the jobvite field is "location_x0020_filter"

Comment 7

[Osmose [:osmose, :mkelly]]

(In reply to Ben (:bensternthal) from comment #5)
> Mkelly - any issues with the additional field items mat mentions above?

Yeah, are you asking for those to be available choices on the site, values available in jobvite, or both?

If we want them as values in Jobvite, we'll probably have to add Latin America as a choice on the website, and probably North America / Europe as well.

If we want them as choices on the site, we'll have to add Latin America as a value in Jobvite.

Comment 8

[Mathew Caldwell]

Yes, that is correct. I would like them both on the site and in the location filter drop down field in JV. I also agree, we need Latin America, North America and Europe options as well.

Comment 9

[[github robot]]

Commit pushed to master at https://github.com/mozilla/lumbergh

https://github.com/mozilla/lumbergh/commit/23a2bb63f8e1cefbbac533f9e4fe0d0050e0fc21
Fix bug 914839: Bay Area, North America, Europe, Latin America filters.

Comment 10

[Ben (:bensternthal)]

Testing this locally I had to run:

./manage.py syncjobvite

To get position.location_filter populated. This field is not populated currently on dev so the dropdown filter can not be tested.

Comment 11

[Osmose [:osmose, :mkelly]]

The root cause of the issue is that dev (and possibly stage and prod) is pointing to the old jobvite feed in the local settings.

I've filed bug 929859 to fix this permanently for dev and stage, but in the short term I was able to sync the jobs for dev using the updated setting once; a cron job might wipe this out within 24 hours. Feel free to reopen if that happens and we need to fix it again.

Comment 12

[Ben (:bensternthal)]

Jobs updated in prod.