This epic includes enhancements to the `CI/CD > Artifacts` page for a project. ## Problem to solve The current artifact page does not show enough data to deliver on a meaningful context for users to decide if they need to for example delete it. We've heard from users that additional information that would allow them to trace the artifact back to a pipeline, commit, user, etc. would be helpful when analyzing them. This was noted in https://gitlab.com/gitlab-org/ux-research/-/issues/1679. ## Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ## JTBD `When new or existing jobs are failing, I want to be able to easily trace the failures back to code, so that I can fix them quickly and get back to pushing features into production.` ### User stories - `When my team runs a pipeline and receives a failure, I need to easily access the related artifacts of the failed job or pipeline, so I can debug the failure.` - `When my team runs a pipeline, I need the job or pipeline artifacts to be traceable back to the originating job or pipeline, so our developers can efficiently package software.` ## Solution validation for this feature https://gitlab.com/gitlab-org/ux-research/-/issues/1859