Is your feature request related to a problem? Please describe.
In my use case, I have a metadata (currently: name of the analysed package) that connects related submissions. I also use it later for finding submissions, as well as semi-automatic archiving in an external storage. In a more generic use case, you can model it as a ticket number from an external system, that can be used to track all submissions related to the given ticket.
Thanks to an option to manually provide metadata, I can always set it when going through submission view. However, it would be extremely useful if those metadata fields were propagated automatically when going to a resubmission of a file or or submitting an extracted URL from the context of a particular submission. Interestingly, it already works like this for files when choosing "Resubmit for Dynamic Analyze", but not with "Adjust parameters before submission".
To be clear: I'm considering transferring some submission metadata to a re-submission of any file from generated in the submission, not only the original file, but also anything extracted. It happens quite often that I want to e.g. submit a file to a dynamic analysis or submit a statically extracted URL. Currently, I have to copy the metadata field each time and then fill it.
Describe the solution you'd like
Allow configuring "sticky" metadata.
Being in a submission view in the UI, when resubmitting any of extracted files, ensure pre-filling configured metadata from the open submission.
Being in a submission view in the UI, when submitting an extracted URL from tags (right click / Submit URL), ensure pre-filling configured metadata from the open submission.
Describe alternatives you've considered
In some cases or views (e.g. file view) it may not be clear which submission should be the "context", so nothing should be pre-filled.
Files can be extracted from many submissions, and it's alright that metadata would be only from a particular one submission: it's about connecting related submissions. If I trigger a submission from a view of another, I'd like to be able to connect them.
An alternative idea would be to introduce "parent" submission - a triggered submission could keep the ID of the previous one (similarly to the ingest ID). However, I think keeping some metadata would be more flexible.
It could also be considered keeping all submission metadata, but I think it may provide unexpected consequences (e.g. copying ingest ID would rather be against the meaning of the metadata).
Additional context
For me, it's important that any extracted file / URL could keep some metadata. It's easier to remove them as to copy and put again ;)
Is your feature request related to a problem? Please describe. In my use case, I have a metadata (currently: name of the analysed package) that connects related submissions. I also use it later for finding submissions, as well as semi-automatic archiving in an external storage. In a more generic use case, you can model it as a ticket number from an external system, that can be used to track all submissions related to the given ticket.
Thanks to an option to manually provide metadata, I can always set it when going through submission view. However, it would be extremely useful if those metadata fields were propagated automatically when going to a resubmission of a file or or submitting an extracted URL from the context of a particular submission. Interestingly, it already works like this for files when choosing "Resubmit for Dynamic Analyze", but not with "Adjust parameters before submission".
To be clear: I'm considering transferring some submission metadata to a re-submission of any file from generated in the submission, not only the original file, but also anything extracted. It happens quite often that I want to e.g. submit a file to a dynamic analysis or submit a statically extracted URL. Currently, I have to copy the metadata field each time and then fill it.
Describe the solution you'd like
Describe alternatives you've considered
Additional context For me, it's important that any extracted file / URL could keep some metadata. It's easier to remove them as to copy and put again ;)