Job export and import requires custom steps? (Feature request)

One workflow might be to export the results of a job from a project PXX, and then to use that as an import into a project PYY.

Currently, this appears to require that the user export the job in PXX. Then manually, there must be created a symlink or copy of the exported job underneath the PYY/exports folder. It is not possible to directly import from the location under the other project PXX.

Could the import of a job results from another project automatically handle this process to create PYY/exports, and symlink PYY/exports/jobXX → PXX/exports/jobXX ?

That would avoid requiring any extra steps and allow the export/import of jobs to work more as users are expecting this to behave.

Thanks!

1 Like

Thanks @larsonmattr for these suggestions.

1 Like