-
Notifications
You must be signed in to change notification settings - Fork 465
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
Policy > Manage automations: maintainers can't turn on/off calendar automations for policies #23448
Comments
Please add your planning poker estimate with Zenhub @jacobshandling |
Add quick test if time allows |
I just tested this manually, maintainers have access to the API for install software and run script but not for calendar events and other workflows ( I'm thinking for maintainers, we should show to the dropdown but disable calendar events and other workflows with a tooltip OR we should remove calendar events and other workflows from the dropdown. wdyt? @rachaelshaw / @noahtalerman Visual of admin dropdown and what works for maintainers and what doesnt: |
Adding this to my plate since I think we should get this into 4.60 major release as we are preventing major flows for maintainers in the UI that are available in the API. |
Here's the permissions we have documented, looks like this doesn't quite match up with what @RachelElysia found (says maintainers can manage calendar events): |
@rachaelshaw Calendar events permissions mismatch is covered in #23483. The issue there is that the current modal covers both things that a maintainer is allowed to do (toggling per policy) and things that require an admin (setting the web hook and turning on/off calendar integrations entirely). |
Check other workflows APIs if maintainer has access to either of them |
@rachaelshaw decide if we should try to fix in 4.60 |
related to #23483 |
Per our discussion, I've created the following two wireframes:
LMK what you think. I'm also not sure of the process on how to move tickets along. I'm assuming this ticket should not move until we've all approved the above, after which I'll move these sections to the "Ready" page? |
Adding to my plate since I already started this and a little blocked this morning on any current tickets. |
I was able to implement as you described and looks good to me! @eugkuo |
QA Notes:
|
@eugkuo and @RachelElysia |
@jmwatts Weird that this would have just "happened." I don't mind keeping the 'Manage automations' UI there when 'All teams' is selected so stuff doesn't appear and disappear off the screen. But if I were to do this, I would grey out the 'Manage automations' entirely with a tooltip to select a team in cases where everything underneath is in the same state. Is this something that was introduced with this ticket? @RachelElysia thoughts? |
The last few comments relate to a new issue that has not been created just yet. The original issue has been fixed with the PR attached. Moving this to Ready for Released. I'll attach the new ticket as a comment once it's been created to track the above. |
Maintainers find peace, |
Fleet version: 4.57.0+ (installs), 4.58.0+ (scripts)
💥 Actual behavior
Per @RachelElysia's comment, maintainers can't set policy automations for software installs or script runs in the UI, though they can in the API. Per today's design review outcome, the API permission is the reasonable one here, so we should match that in the UI.
🧑💻 Steps to reproduce
🛠️ To fix
Per our discussion, I've created the following two wireframes:
Calendar event modal for maintainer roles
Mange automations dropdown for maintainer roles
The text was updated successfully, but these errors were encountered: