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

Copy Settings Documentation #226

Open
2 tasks done
BigRoy opened this issue Aug 28, 2024 · 0 comments · May be fixed by #298
Open
2 tasks done

Copy Settings Documentation #226

BigRoy opened this issue Aug 28, 2024 · 0 comments · May be fixed by #298
Labels
Admin Docs documentation Improvements or additions to documentation Server type: enhancement New feature or request

Comments

@BigRoy
Copy link
Contributor

BigRoy commented Aug 28, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

There are a lot of different Settings in AYON.

  • Anatomy
  • Studio Settings
  • Project Settings

And there are a lot of ways to "copy paste" these types of settings, and potentially more coming with ynput/ayon-frontend#752 and reported here we may need to document the different types of "Settings Management" and how to copy e.g. specific settings that you'd want from one place to another.

But a user may also face issues with Copy and Paste in the settings pages as this issue describes: ynput/ayon-frontend#762
So we may want to also highlight that and maybe have some graphics displaying how to enable that using tip section in the documentation.

How would you imagine the implementation of the feature?

We may need some very clear wording in the documentation that we have a few levels of granularity to copying settings:

  1. Copy settings from... on bundles page copies all studio settings and project overrides for that bundle* (not released yet)
  2. Copy settings from... on studio settings page copies only the studio settings between the bundles
  3. Copy settings from... on studio settings page on a particular addon copies between studio settings for only a specific addon version.
  4. Copy settings from... on project settings page copies only the project settings for the selected project between the bundles.
  5. Copy settings from... on project settings page on a particular addon copies project overrides for only selected project for only specific addon version.

The "Copy Settings" toggle on creating a new bundle is basically that top one (number 1) described above - it will copy all studio settings and project setting overrides between the bundles.

That's a lot of different dialogs we have. And someone may be as stupid as me and definitely at one point will by accident be using the wrong page, using the wrong dialog unintentionally.

Also #219 will be crucial because to understand settings we'd also need to document that

  • Addons have settings PER variant PER addon version.

Because that is the hardest concept to grasp that you're copying to variant for each addon version... and not to the bundle.

Are there any labels you wish to add?

  • I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

Better settings UIs and dialogs will definitely help already.

Additional context:

The current settings documentation is old anyway, with screenshots that come mostly from OpenPype's Qt dialogs still: https://ayon.ynput.io/docs/admin_settings

So some love for this page is more than welcome!

Issues with Copy & Paste also came up on the forum

@BigRoy BigRoy added documentation Improvements or additions to documentation type: enhancement New feature or request Server Admin Docs labels Aug 28, 2024
@MustafaJafar MustafaJafar linked a pull request Oct 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Docs documentation Improvements or additions to documentation Server type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant