The dashboard's attention rail summed DMARC and TLS report warnings into one item across every domain, so "12 reports with warnings" read as disagreeing with the DMARC reports page, which shows one domain at a time.
Two items now: "N DMARC reports with warnings" and "N TLS reports with warnings", each shown only when its count is above zero and each linking to its own reports page.
Each detail line says the count covers all domains over the dashboard's period.
The old combined cc.a.reports* strings are gone from en.json.
Wording stays "with warnings", matching the counters behind it (incoming-report.*-report-with-warnings). A TLS report counted more than once is a server matter, inbuxa-server#402.
Checked locally: typecheck, lint, i18n:check, tests (1121, 2 new), the three shell tests, build, notice-check.
Fixes #218 (forum t/232, post 27).
The dashboard's attention rail summed DMARC and TLS report warnings into one item across every domain, so "12 reports with warnings" read as disagreeing with the DMARC reports page, which shows one domain at a time.
- Two items now: "N DMARC reports with warnings" and "N TLS reports with warnings", each shown only when its count is above zero and each linking to its own reports page.
- Each detail line says the count covers all domains over the dashboard's period.
- The old combined `cc.a.reports*` strings are gone from en.json.
Wording stays "with warnings", matching the counters behind it (`incoming-report.*-report-with-warnings`). A TLS report counted more than once is a server matter, inbuxa-server#402.
Checked locally: typecheck, lint, i18n:check, tests (1121, 2 new), the three shell tests, build, notice-check.
The attention rail added DMARC and TLS report warnings into one count
across every domain, so "12 reports with warnings" read as disagreeing
with the DMARC reports page, which lists one domain at a time. Each kind
now gets its own item, linking to its own reports page, and says the
count covers all domains over the dashboard's period.
Fixes#218
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #218 (forum t/232, post 27).
The dashboard's attention rail summed DMARC and TLS report warnings into one item across every domain, so "12 reports with warnings" read as disagreeing with the DMARC reports page, which shows one domain at a time.
cc.a.reports*strings are gone from en.json.Wording stays "with warnings", matching the counters behind it (
incoming-report.*-report-with-warnings). A TLS report counted more than once is a server matter, inbuxa-server#402.Checked locally: typecheck, lint, i18n:check, tests (1121, 2 new), the three shell tests, build, notice-check.