Back to journal

Saved alerts should show what was saved

On November 13, I changed the summaries of saved job alerts in Seasonal.Work. Two searches could share a keyword and location while differing in job type or pay requirements. If the list showed only their common fields, they could look identical even though the saved criteria were different. The correction made those existing differences visible.

The alert list already showed details such as keyword, location and seasonal preferences. I connected it to the existing summary builder so job types, monthly pay bounds and hourly-rate bounds could appear alongside those details. This reused the application's established description of search criteria instead of maintaining a shorter, separate interpretation for the saved-alert screen. The saved search itself was not rewritten.

Pay criteria need more than one display case. A search can have both ends of a range, only a minimum or only a maximum. It can also contain pay criteria without a keyword. The added cases check those combinations, including a valid zero minimum, so a meaningful bound is not accidentally treated as absent. An alert with genuinely empty criteria keeps the existing general description. The label should summarize the data available, not fill gaps with guessed preferences.

The change was integrated on November 13, with coverage showing that two otherwise similar alerts remain distinguishable by type and pay. Rendering the labels does not make another request or change the matching rules. That is the useful scope of the correction: someone returning to a saved-alert list can read more of the choices already stored, without needing a new editing flow simply to understand what they created.

Reflection

A saved item is only easy to manage when its summary preserves the distinctions that matter. In Seasonal.Work, exposing existing job-type and pay criteria made the list more informative while keeping the underlying searches unchanged.