Bug #4289
open
[Workbench] Job view should include the relevant component name(s) from each pipeline where the job was used
0%
Description
There is a list of pipelines that used the job, but they don't show the name of the relevant component.
It's probably common for a job to have the same component name in all of the pipelines where it has been used. In that case, we might as well show that name instead of the heading "this job".
If we don't have anything better to say, "Job {uuid}" would be more useful than "this job".
Original report:
When having this job 8555b7122bea802f5570203e89669e2f.png and clicking on the uuid to bring up the job page, the name should match acea9e5e9e5d45b7610dde5c3b5b4733.png so that we can know what job we're looking at
Files
Updated by Bryan Cosca about 10 years ago
When having this job 
and clicking on the uuid to bring up the job page, the name should match 
so that we can know what job we're looking at
Updated by Radhika Chippada
Updated by Ward Vandewege about 10 years ago
- Subject changed from Job names should match to [Workbench] Job names should match
Updated by Brett Smith about 10 years ago
- Subject changed from [Workbench] Job names should match to [Workbench] Job view should include the job's full name instead of "this job"
Updated by Tom Clegg about 10 years ago
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Tom Clegg about 10 years ago
- Subject changed from [Workbench] Job view should include the job's full name instead of "this job" to [Workbench] Job view should include the relevant component name(s) from each pipeline where the job was used
- Description updated (diff)
- Category set to Workbench
Updated by Ward Vandewege over 3 years ago
- Target version deleted (
Arvados Future Sprints)