Skip to content

[Feature]: Expose jobName on running-jobs API response (#3455)#1801

Draft
markus-moser wants to merge 2 commits into2025.4from
feature/rehydrate-running-jobs-expose-job-name
Draft

[Feature]: Expose jobName on running-jobs API response (#3455)#1801
markus-moser wants to merge 2 commits into2025.4from
feature/rehydrate-running-jobs-expose-job-name

Conversation

@markus-moser
Copy link
Copy Markdown
Contributor

Companion backend change for studio-ui-bundle fix of #3455.

Changes

  • JobRun schema: adds required jobName: string property
  • JobRunListHydrator: populates jobName from $jobRun->getJob()?->getName()

The frontend uses this field to route each in-progress job to the correct rehydration handler on page reload.

Adds the job name to the running-jobs list endpoint so the frontend
can route each in-progress job to the correct rehydration handler on
page reload, fixing issue #3455.
@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 30, 2026

Not up to standards ⛔

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

When the request body contains no filters object, CollectionFilterParameter
returns null from getFilters(). Use a default FilterParameter instance as
fallback so pagination and sort don't throw a null pointer exception.
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant