FlexMeasures / flexmeasures / 34466339144

85%

push

github

Status page: include the jobs of sub-assets (optional) (#2500)

* ui/status: list the jobs of sub-assets, too

Context:
- Issue #2447: it is not always clear on which level a schedule is triggered,
  so someone looking at a site asset misses the jobs that ran on its children.

Change:
- Let build_asset_jobs_data() walk the asset's offspring, which the jobs
  endpoint does by default and skips on include_child_assets=false.
- Offer the choice on the jobs tab of the status page, for assets that have
  sub-assets, and remember it in the user's session, as we do for the tab itself.
- Add POST /api/v3_0/assets/status_page_child_jobs to record that preference.

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

* tests: cover the jobs of sub-assets on the status page

Context:
- Issue #2447 lets the jobs tab of a status page report what happened on the
  asset's sub-assets as well.

Change:
- Assert that a parent asset reports a job triggered on its child, both from
  build_asset_jobs_data() and from the jobs endpoint, and that both leave it
  out when the child assets are excluded.
- Assert that the page offers the choice only where there are sub-assets, that
  it defaults to including them, and that it follows the session.
- Assert that the new endpoint stores the choice in the session.

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

* docs: document the jobs of sub-assets on the status page

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

* ui/status: name the asset each job happened on

Context:
- Review on PR #2500: now that a site asset lists the jobs of everything below
  it, the table should say which asset each job happened on. The Entity column
  does not answer that for a sensor job, whose sensor may sit on any descendant.

Change:
- Report asset_id and asset_name per job, taken from the asset the job was
  collected from rather than the one that was asked about, and show them in a
  new Asset column, linking to that asset.
- E... (continued)

27 of 27 new or added lines in 2 files covered. (100.0%)

18842 of 22084 relevant lines covered (85.32%)

0.85 hits per line