The console side of scheduled reports and the weekly digest (roadmap 17 + 14). Needs inbuxa-server #160; against an older server the page says it isn't there yet.
Reports › Scheduled (the menu link comes from the server, #160)
a card per report, the digest first (marked built in): schedule in words ("Every Monday at 07:00 (UTC)"), who gets it (the digest: "the system administrators"), section chips, next run (local time), last run (sent to N / failed with the server's reason), on/off switch
Edit / New report: name; sections, each with what it contains; daily / weekly / monthly at a time in a time zone (the browser's to start, searchable list); recipients one per line (accounts on this server only; the server's refusal shows in the dialog); CSV files. A tenant admin's editor greys out the server-wide sections.
Send now; Download: last full period, last 7 / 30 days, or picked dates (≤ 90 days) as a ZIP; Delete with the Undo toast (not for the digest)
Who reports come from (name, address), for server administrators only (only they can see the digest, which is the signal)
RP-17: a report whose last two scheduled runs failed shows the reason on its card and goes to the dashboard's Needs attention (cc.a.scheduledReports; note cc.a.reports was already taken by "reports with warnings")
Translation: 89 new strings in en.json (schedRep.*, sched.*, cc.a.scheduledReports*), English only for now.
Checked locally: typecheck, lint, i18n:check, 637 tests (6 new: schedule wording, the RP-17 rule, recipients, zones; attention item), build, notice-check. Previewed against the #160 server build: menu link under Reports; the digest card; New report with an outside recipient (refused, reason shown) then a local one (created, Phoenix time); Send now (ran; failed with "localhost.local has no DKIM key" — correct for that preview); Download (ZIP with summary.txt); Delete → Undo → Delete.
The console side of scheduled reports and the weekly digest (roadmap 17 + 14). **Needs inbuxa-server #160**; against an older server the page says it isn't there yet.
**Reports › Scheduled** (the menu link comes from the server, #160)
- a card per report, the digest first (marked built in): schedule in words ("Every Monday at 07:00 (UTC)"), who gets it (the digest: "the system administrators"), section chips, next run (local time), last run (sent to N / failed with the server's reason), on/off switch
- **Edit / New report**: name; sections, each with what it contains; daily / weekly / monthly at a time in a time zone (the browser's to start, searchable list); recipients one per line (accounts on this server only; the server's refusal shows in the dialog); CSV files. A tenant admin's editor greys out the server-wide sections.
- **Send now**; **Download**: last full period, last 7 / 30 days, or picked dates (≤ 90 days) as a ZIP; **Delete** with the Undo toast (not for the digest)
- **Who reports come from** (name, address), for server administrators only (only they can see the digest, which is the signal)
- **RP-17**: a report whose last two *scheduled* runs failed shows the reason on its card and goes to the dashboard's Needs attention (`cc.a.scheduledReports`; note `cc.a.reports` was already taken by "reports with warnings")
Translation: 89 new strings in en.json (`schedRep.*`, `sched.*`, `cc.a.scheduledReports*`), English only for now.
Checked locally: typecheck, lint, i18n:check, 637 tests (6 new: schedule wording, the RP-17 rule, recipients, zones; attention item), build, notice-check. Previewed against the #160 server build: menu link under Reports; the digest card; New report with an outside recipient (refused, reason shown) then a local one (created, Phoenix time); Send now (ran; failed with "localhost.local has no DKIM key" — correct for that preview); Download (ZIP with summary.txt); Delete → Undo → Delete.
Each report with its schedule in words, who gets it (the digest: the
system administrators), what it covers, when it goes next and how the
last run went, with an on/off switch, Edit, Send now, Download and
Delete with Undo. The editor explains each section, offers daily, weekly
or monthly at a time in a time zone (the browser's to start), and takes
recipients that must be accounts on this server; a tenant's report
leaves out the server-wide sections. Download builds the report for its
last period, the last 7 or 30 days, or picked dates, as a ZIP. Server
administrators set who reports come from. A report whose last two
scheduled runs failed shows why on its card and on the dashboard's
Needs attention.
Needs inbuxa-server's scheduled reports (server #160); an older server
gets a line saying so.
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.
The console side of scheduled reports and the weekly digest (roadmap 17 + 14). Needs inbuxa-server #160; against an older server the page says it isn't there yet.
Reports › Scheduled (the menu link comes from the server, #160)
cc.a.scheduledReports; notecc.a.reportswas already taken by "reports with warnings")Translation: 89 new strings in en.json (
schedRep.*,sched.*,cc.a.scheduledReports*), English only for now.Checked locally: typecheck, lint, i18n:check, 637 tests (6 new: schedule wording, the RP-17 rule, recipients, zones; attention item), build, notice-check. Previewed against the #160 server build: menu link under Reports; the digest card; New report with an outside recipient (refused, reason shown) then a local one (created, Phoenix time); Send now (ran; failed with "localhost.local has no DKIM key" — correct for that preview); Download (ZIP with summary.txt); Delete → Undo → Delete.