-
Notifications
You must be signed in to change notification settings - Fork 112
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
Extend Comments section with Use cases #467
base: 4.19
Are you sure you want to change the base?
Conversation
@blueorangutan docbuild |
@nvazquez a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/467. (QA-JID 297) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- we need to clarify that users and admins can only add comments to objects they have the privileges to access!
- some comments can be "admin-only", do we need to also think about what the domain admins can read/write, should a similar capability be extended to them?
Co-authored-by: NuxRo <[email protected]>
@blueorangutan docbuild |
@nvazquez a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/467. (QA-JID 298) |
@nvazquez , this is how it is intended, isn't it? not how it works atm! |
@DaanHoogland yes, but mostly its how its working besides the bug found, I'll add some additional notes or warnings |
📚 Documentation preview 📚: https://cloudstack-documentation--467.org.readthedocs.build/en/467/