v2.7.0

Jamf Reports 2.7.0 is about trusting the numbers on a folder several Macs share. The whole workspace can now live on a synced team folder, reports can cover a period instead of a moment, and the app tells you, on every screen, when a data source has stopped landing. It also absorbs the Jamf Platform API's move to general availability and tracks jamf-cli 1.28.0.

Shared workspaces

Pick a folder under Settings → Workspace location — OneDrive, SharePoint, Box, Dropbox, Google Drive or a mounted share — and every Mac pointed at it builds one pooled history. On a synced folder, coordination switches itself on: a scheduled collect stands down when another Mac collected recently, naming which one and when, and each run publishes a short claim so a second machine can see one is already working. Pressing Refresh always collects anyway. Backup retention works on a shared folder again; each Mac prunes only its own backups.

Choosing a shared folder asks you to confirm it and names what becomes readable to everyone with access: device serials, usernames, email addresses and any configured webhook URL. If colleagues only need the finished reports, the narrower option is still there and still preferred: keep the workspace local and point output.output_dir at the shared folder with output.allow_absolute_paths: true. Coordination covers Jamf Pro collects; a Jamf School profile on a shared folder is not coordinated.

Period reports

From the Reports screen, choose a rolling window (4, 12, 26 or 52 weeks) or a calendar one (last full month, last full quarter, or your own dates) and get a workbook with a start figure, an end figure and the change for each metric. Every figure carries the date it actually came from, and a boundary that had to move more than three days to find data says so. Extension attributes are opt-in, counted against the value you configured as good or broken down by value, and the picker warns when an attribute looks like an identifier rather than a status.

Know when data stops landing

A strip across the top of the window reports data sources that are failing or far behind schedule, whatever screen you are on, with a Collect now button. While the app is open it re-collects only the sources that are behind, at most once an hour, and within a run a source that fails on a timeout or rate limit is retried once; authentication and permission failures are never retried. A run that served stale cache for any source now says so in Run History instead of finishing green, and a run where jamf-cli could not be started at all no longer writes a day's summary from old cache or sends a success notification.

Sharper checks

Run check on the Config screen, and jamf-reports check --json from Terminal, now run every validation the app has: column mappings that no longer match your CSV, baselines pointing at uncollected attributes, malformed alert rules, data-accuracy problems and the state of the workspace folder, each with a concrete fix. Two new checks recognise a workspace that is fine but not the one you expected: more history for the profile in another folder, or a brand-new workspace still on defaults. Scheduled runs record failing config checks in their own log.

Backup diffs you can read

Comparing two backups shows what actually changed instead of the full configuration of every changed object; on a real pair of production backups that turns ten screens of JSON into two lines. Password hashes, recovery keys and pre-shared keys are redacted in the summary and the Copy button. The Raw view is one click away and unredacted, for scripting against.

On-device AI only

Apple Foundation Models is on-device only, so the Private Cloud Compute option and its lock switch are gone. Existing configs keep loading and are tidied on the next save.

jamf-cli 1.28.0 and the Platform API

The Jamf Platform API reached general availability on 1 September. Sign-in screens now prefill the current gateway address, a command jamf-cli refuses on a Platform profile (its new exit code 8) is explained in plain language and not retried automatically, and on a Jamf Pro profile without Platform access the four Platform-only sources are skipped rather than failed every day. Tracks jamf-cli 1.28.0; 1.18.0 remains the floor.

Fixed

• A CSV dropped in csv-inbox/ older than stale_device_days is skipped and named, instead of marking a fleet stale and resurrecting retired Macs.
• Turning on require_manifest no longer empties the Devices screen.
• Every dashboard, the workbook and the HTML report pick snapshots by filename, and sync-conflict copies are ignored everywhere.
• Backups are pruned by folder timestamp, not modification date, and never on another Mac's behalf.
• The Patch Failures sheet returns on jamf-cli 1.24 and later.
• Three crashes found on a shared production workspace: duplicate extension-attribute names, a run-log write on an evicted file, and a CSV with two columns differing only in case.
• Run History no longer reports a schedule interval as a run duration.
• Overview tiles name the day their change compares against.
• The two chart switches in Customize now persist, and charts.save_png is honoured; if your config already says save_png: false, standalone PNGs stop appearing.
• Device Lookup and the Devices detail panel work again around a jamf-cli --out-file bug.

Known issues

• On jamf-cli 1.24.0 through 1.27.0, pro report security requires a Jamf Security Cloud subscription, so Security Posture and every FileVault, SIP, firewall and Gatekeeper figure show their last collected values and the strip reports security as failing. jamf-cli 1.28.0 fixes this; upgrading restores all of it.
• Environment- and organization-scoped Platform API credentials are not yet supported by onboarding; tenant scope is.
• On a Jamf Pro instance that does not serve inventory v4, confirm a collect still fills the Devices screen after upgrading to jamf-cli 1.28.0.

Compatibility

macOS 14 or later. jamf-cli 1.18.0 or later; tracks 1.28.0. Existing workspaces and LaunchAgents are unaffected; the workspace stays at ~/Jamf-Reports until you move it.

Downloads

File	What it is
JamfReports-2.7.0.pkg	Installer package, notarized and stapled
JamfReports-2.7.0.dmg	Disk image, notarized and stapled
SHA256SUMS	Checksums for every asset on this page

Full details in CHANGELOG.md.