Seqera Platform Feature Requests

Currently, every page on the Seqera Platform displays the title "Seqera Cloud", which isn't particularly helpful in understanding where in the platform the user is located. This should reflect where in the hierarchy the user is located, for example Seqera Platform | <org-name> | <wksp-name> | <section> | <ID> where section is Compute Environments , Data Studios , Runs for example, and ID is the specific detail-view page.

Currently with AWS Batch executor if the head job dies (e.g. OOM), remaining in-flight compute jobs continue running and are not cancelled. Tower would ideally kill the child compute jobs when the parent has died (I believe it already tracks the native task IDs from batch).

After I generate a container on Seqera Containers, there is no way to share it with a collaborator except the URI to the container image itself. Instead, it would be great to share a link to the Seqera Container page with the build details etc. This would allow other users to check the build details before pulling the image.

Although the Open API docs exist, there are no details on the fields themselves (e.g. when to use it, why to use it, what are its limitations etc) that could provide information about the nf-tower maps and their field limits and size.

It will be very nice if the Seqera favicon of the Pipeline Run page and Data Studios page shows a small dot orange/blue/red/green depending on the run status. Like Github actions status page does.

To help track and manage costs, all Data Studio components should be tagged with resource labels when adding the session. This includes: the compute environment jobs containers