Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

save form options as profile #1500

Open
3 of 5 tasks
johrstrom opened this issue Oct 25, 2021 · 1 comment · Fixed by #2958
Open
3 of 5 tasks

save form options as profile #1500

johrstrom opened this issue Oct 25, 2021 · 1 comment · Fixed by #2958
Assignees
Labels
component/batch_connect enhancement This is functionality that builds upon existing functionality. epic Very large tickets
Milestone

Comments

@johrstrom
Copy link
Contributor

johrstrom commented Oct 25, 2021

This feature would allow you to save form options as a so called 'profile'. Let's take the simple example of large and small. Large makes requests for 48 cores the other only 1.

How to save, edit and delete them is unclear. Maybe this feature could start in the new job composer and then migrate to batch connect when it coalesces with whatever abstraction comes out of the job composer.

Here's the discourse topic the idea came from:
https://discourse.osc.edu/t/what-save-form-options-as-profilef-we-combined-job-templates-and-interactive-app-forms/1749

┆Issue is synchronized with this Asana task by Unito

@johrstrom
Copy link
Contributor Author

This isn't a job composer thing - it's more like a favorite setting. Think "all the options I like to save to launch Jupyter".

new job composer and then migrate to batch connect when it coalesces
probably the other way around? Or probably more accurately - seperate things entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/batch_connect enhancement This is functionality that builds upon existing functionality. epic Very large tickets
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants