Donate to Postulo/postulo

• https://buymeacoffee.com/tiagoagueda

---

See the documentation for more details on donation links.

Let a status or a channel have its own number of days before quiet #1233

Merged

tiagoagueda merged 2 commits from f-1099 into main 2026-11-12 01:47:23 +00:00

Conversation 0 Commits 2 Files changed 103 +6336 -22

tiagoagueda commented 2026-11-11 22:44:16 +00:00

Owner

• Copy link
• Copy Markdown

Closes #1099: an application can go quiet after a different number of days for each status, or for what it was applied through.

• Settings → Appearance → Gone quiet gains number boxes per status (Applied, Screening, Interviewing, Assessment, Offer) and per channel; blank means the usual number. A status's number comes before a channel's, which comes before the usual one (the issue's decision).
• The rule is one SQL condition read off the profile each owner already comes with: the gone-quiet pass stays at 1 + N queries for N accounts (#1120's tests unchanged, one new test with numbers set).
• Each open, sent application's Move it along card says when it counts as quiet and which number applies. The board, the table filter and the API's ?quiet=true use the same rule. When the numbers vary, the dashboard widget and the sources table stop naming a single number.
• Two profile fields (accounts 0052_quiet_days_by_status_and_channel), archive format 81; on import, unknown keys and numbers outside 1–365 are dropped.

Choices left open for review: Acknowledged has no box of its own (the issue lists five statuses); all page wording is new and worth a read; per-application numbers are not built (the issue's decision).

Tested: 10 new tests fail without the change; the quiet, export, settings, widgets and dashboard tests and 70 browser tests on the touched pages (axe, reflow, target size, right to left) pass. New strings are extracted for Weblate.

🤖 Generated with Claude Code

Closes #1099: an application can go quiet after a different number of days for each status, or for what it was applied through. - Settings → Appearance → *Gone quiet* gains number boxes per status (Applied, Screening, Interviewing, Assessment, Offer) and per channel; blank means the usual number. A status's number comes before a channel's, which comes before the usual one (the issue's decision). - The rule is one SQL condition read off the profile each owner already comes with: the gone-quiet pass stays at 1 + N queries for N accounts (#1120's tests unchanged, one new test with numbers set). - Each open, sent application's *Move it along* card says when it counts as quiet and which number applies. The board, the table filter and the API's `?quiet=true` use the same rule. When the numbers vary, the dashboard widget and the sources table stop naming a single number. - Two profile fields (`accounts 0052_quiet_days_by_status_and_channel`), archive format 81; on import, unknown keys and numbers outside 1–365 are dropped. Choices left open for review: Acknowledged has no box of its own (the issue lists five statuses); all page wording is new and worth a read; per-application numbers are not built (the issue's decision). Tested: 10 new tests fail without the change; the quiet, export, settings, widgets and dashboard tests and 70 browser tests on the touched pages (axe, reflow, target size, right to left) pass. New strings are extracted for Weblate. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

tiagoagueda added 2 commits 2026-11-11 22:44:16 +00:00

Let a status or a channel have its own number of days before quiet ... 6b02061a37

An application went quiet after one number of days, the same for every
application. One sent through a recruiter, one at screening and one after
a final interview do not go quiet at the same pace.

Under Settings, Appearance, beside the usual number, there is now a box
for each status that can have one (applied, screening, interviewing,
assessment, offer) and for each way of applying. Blank means the usual
number. A status's number comes first, then the channel's, then the usual
one. They are stored on the profile as two mappings, travel in the archive
(format 81) and are checked on the way back in.

The rule is one condition in SQL: a disjunction over the numbers set,
each guarded by the ones that win over it, and the same single comparison
as before when none is set. It is read off the profile that already comes
with each owner, so the gone-quiet pass still asks 1 + N queries for N
accounts (#1120), and the board, the table, the API, the dashboard and the
figures all use it. The figures' cache key carries the new numbers.

Each application's page now says when it counts as quiet and which number
gave that day, or that something planned keeps it from being quiet. The
dashboard's quiet widget and the sources table stop naming one number of
days once some applications are held to another.

Closes #1099

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Record #1099 in the changelog and extract its strings ... 928441aad6

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

tiagoagueda referenced this pull request 2026-11-11 22:54:39 +00:00

Follow calendars somebody else keeps, read-only #1234

tiagoagueda merged commit 928441aad6 into main 2026-11-12 01:47:23 +00:00

tiagoagueda deleted branch f-1099 2026-11-12 01:47:26 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

accessibility

Usable by everyone, including people with disabilities: one of the project's stated missions

  

authentication

Signing in, and proving who you are

  

breaking change

Changes behaviour or data in a way operators must act on

  

bug

Something does not do what it says it does

  

documentation

The wiki, the docs, or the words in the interface

  

enhancement

An improvement or a new capability

  

interface

The shape of the pages: what is where, and how it reads

  

internationalisation

Languages, regions, and the formats and symbols that go with them

  

observability

What an operator can see about a running instance: metrics, logs, health

  

performance

Uses fewer resources, or is more reliable, with no loss of features or accessibility

  

security

Keeping the code and the data secure: one of the project's stated missions

  

tier

1

Easy: small, self-contained, no prerequisites

  

tier

2

High-severity security: account access, personal data, the boundaries

  

tier

3

Foundations: prerequisite work that unblocks other issues

  

tier/4

Later: large features and long-horizon work

No labels

accessibility

authentication

breaking change

bug

documentation

enhancement

interface

internationalisation

observability

performance

security

tier

1

tier

2

tier

3

tier/4

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Postulo/postulo!1233

No description provided.