Hi,
I have some workspaces that contain linked jobs from other workspaces. When I enter tree view, all jobs that are connected to the linked job, even those from other workspaces, show up in the tree view for that workspace. I think it would be useful to have an option to hide any jobs that are not from or linked to the current workspace in tree view.
Hi @camittacm ,
Thanks for the post! The reason we pull in non-linked jobs within the tree view of another workspace is to ensure that the linked job is not floating on its own and has a clear lineage to an import job. However, I see that sometimes when you’re interested in viewing only jobs from the workspace and linked jobs, this can be confusing. I’ll add a to-do for our team to support hiding these non-linked jobs.
- Suhail
Hi, I encountered the same problem. Has it been solved? I’m currently using cryosparc-v4.7.1
also, is there a way to hide jobs which have been deleted?
The implementation of the workspace view in v4.7 differs from the CryoSPARC version that was current when this forum topic was created.
@J6H55 Please can you post an annotated screenshot that illustrates the problem in v4.7.1?
Please post a screenshot of the workspace that shows a deleted job and the jobs to which it connects. Did you deleted the job through the web interface?
I’ve posted it below, can we hide them now?
You may conceal the screenshots now, if you wish. Or are you referring to something else?
no, I mean when we use treeviews instead of card view, the deleted jobs and parent jobs from another workspace always show out, is there any button to hide them so that we can only see jobs in this very current workspace?
Hi @J6H55 ,
These are fundamental limitations in v4.7 due to the way that job connections are handled.
Jobs that are deleted in-between other jobs are needed to correctly render the tree without causing issues in the underlying algorithm, this is also the case for jobs from other workspaces when they are ancestors of jobs that are in the current workspace.
However, both of these behaviours have been fundamentally changed in CryoSPARC v5.
In v5 jobs cannot be deleted in the middle of chains unless their ancestors have been cleared or are in a building status. If this constraint is met, when a job is deleted all of its references are removed, this means that the tree simply reorganizes itself and the deleted job disappears.
“Upstream” jobs are also handled differently in v5, with jobs that are not in the current workspace being collapsed into grouped cards by default. This is documented in more depth here: Upstream Jobs.
I believe these two changes would largely cover the issues you are experiencing in the provided screenshots and explanation.
It is worth noting that as of writing this, CryoSPARC v5 is still in public beta. There have been multiple bug-fix releases and it is generally stable, but this should be considered before planning an upgrade.
- Kelly
thank you for helping 
