Frontend: Artifacts: Refetch list of jobs on delete so that newly empty jobs disappear
Summary
- After deleting artifacts, the "header" row is maintained in the table but in a disabled state. Curious as to why we don't just remove those on deletion, as when I reload they are then gone. It also seems to cause some doubling up of a border
Why this matters and how we measure
User Stories
Proposal
When artifacts are deleted, refetch the list of jobs via GraphQL so that any jobs that no longer have artifacts disappear from the list, freeing up more space for jobs with artifacts. This should behave the same way as a page refresh currently does, because the GraphQL endpoint only returns jobs that have artifacts now (which was not true when the query was written originally, so we didn't bother refetching).
Performance Considerations
Out of Scope
Acceptance Criteria
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Which tier(s) is this for?
- Additional comments:
Implementation Table
| Group | Issue Link |
|---|---|
| frontend |
|
Links/References
Edited by Miranda Fluharty