<!-- **This issue's remaining effort can be completed in ≤1 sprint. It will be valuable even if nothing else ships.** It is [planned and ready](https://fleetdm.com/handbook/company/development-groups#making-changes) to implement. It is on the proper kanban board. --> ## Goal | User story | |:---------------------------------------------------------------------------| | As a user viewing the activity feed, | I want to see a different default avatar for API-only users | so that I can easily spot changes made by humans in the UI versus changes via the API/GitOps. ## Key result Small UX improvements <!-- What quarterly key result (KR) does this story contribute to, if any? If it doesn't contribute to a KR, explain why it's being prioritized. --> ## Original requests #26921 <!-- Insert the link to the feature request(s) that this story contributes to. Put "None" if it doesn't contribute to a request. For customer requests, add the `customer-xyz` label(s). --> ## Context - Product Designer: @rachaelshaw <!-- Who is the product designer to contact if folks have questions about the UI, CLI, or API changes? --> <!-- What else should contributors [keep in mind](https://fleetdm.com/handbook/company/development-groups#developing-from-wireframes) when working on this change? (Optional.) 1. 2. --> ## Changes ### Product - [x] UI changes: [Figma](https://www.figma.com/design/E8j3ZFwln1gBzVGVuSDs3Y/-27457-Different-default-avatar-for-API-only-users?node-id=27-205&t=ZsoFZnKiVmOuiyOr-1) <!-- Insert the link to the relevant Figma cover page. Make sure wireframes show the UI down to 768px (min screen width). Put "No changes" if there are no changes to the user interface. --> - [x] CLI (fleetctl) usage changes: _No changes_ <!-- Insert the link to the relevant Figma cover page. Put "No changes" if there are no changes to the CLI. --> - [x] YAML changes: _No changes_ <!-- Specify changes in the YAML files doc page as a PR to the reference docs release branch following the guidelines in the handbook here: https://fleetdm.com/handbook/product-design#drafting Put "No changes" if there are no changes necessary. --> - [x] REST API changes: [PR](https://github.com/fleetdm/fleet/pull/28272) <!-- Specify changes in the the REST API doc page as a PR to reference docs release branch following the guidelines in the handbook here: https://fleetdm.com/handbook/product-design#drafting Put "No changes" if there are no changes necessary. Move this item to the engineering list below if engineering will design the API changes. --> - [x] Fleet's agent (fleetd) changes: _No changes_ <!-- Specify changes to fleetd. If the change requires a new Fleet (server) version, consider specifying to only enable this change in new Fleet versions. Put "No changes" if there are no changes necessary. --> - [x] GitOps mode changes: _No changes_ <!-- Specify UI changes for read-only GitOps mode. Put "No changes" if there are no changes necessary. --> - [x] Activity changes: _No changes_ <!-- Specify changes to the Audit log page in the contributor docs. Put "No changes" if there are no changes necessary. --> - [x] Permissions changes: _No changes_ <!-- Specify changes in the Manage access doc page as a PR to the reference docs release branch. If doc changes aren't necessary, explicitly mention no changes to the doc page. Put "No changes" if there are no permissions changes. --> - [x] Changes to paid features or tiers: _No changes_ <!-- Specify changes in pricing-features-table.yml as a PR to reference docs release branch. Specify "Fleet Free" and/or "Fleet Premium" if there are no changes to the pricing page necessary. --> - [x] Transparency changes: _No changes_ <!-- If there are changes to the personal information Fleet can see on end user workstations, make sure wireframes include changes to the My device page. Also, specify changes as a PR to the fleetdm.com/better (aka Transparency page). Put "No changes" if there are no changes necessary. --> - [x] First draft of test plan added - [x] Other reference documentation changes: _No changes_ <!-- Any other reference doc changes? Specify changes as a PR to reference docs release branch. Put "No changes" if there are no changes necessary. --> - [x] Once shipped, requester has been notified - [x] ~~Once shipped, dogfooding issue has been filed~~ N/A (small UX improvement) ### Engineering - [ ] Test plan is finalized - [ ] Contributor API changes: Probably no need. <!-- Specify changes in the the Contributor API doc page as a PR to reference docs release branch following the guidelines in the handbook here: https://fleetdm.com/handbook/product-design#drafting Put "No changes" if there are no changes necessary. --> - [ ] Feature guide changes: No need. <!-- Specify if a new feature guide is required at fleetdm.com/guides, or if a previous guide should be updated to reflect feature changes. --> - [ ] Database schema migrations: Probably not needed. <!-- Specify what changes to the database schema are required. (This will be used to change migration scripts accordingly.) Remove this checkbox if there are no changes necessary. --> - [ ] Load testing: No need. <!-- List any required scalability testing to be conducted. Remove this checkbox if there is no scalability testing required. --> > ℹ️ Please read this issue carefully and understand it. Pay [special attention](https://fleetdm.com/handbook/company/development-groups#developing-from-wireframes) to UI wireframes, especially "dev notes". ## QA ### Risk assessment - Requires load testing: No. <!-- User story has performance implications that require load testing. Otherwise, remove this item. --> - Risk level: Low <!-- Choose one. Consider: Does this change come with performance risks? Any risk of accidental log spew? Any particular regressions to watch out for? Any potential compatibility issues, even if it's not technically a breaking change? --> - Risk description: Risk is limited to the UI icon area. <!-- If the risk level is high, explain why. If low, remove. --> ### Test plan <!-- Add detailed manual testing steps for all affected user roles. --> > Make sure to go through [the list](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/design-qa-considerations.md) and consider all events that might be related to this story, so we catch edge cases earlier. 1. On an older branch, run GitOps with an API-only user configured (and no gravatar set for that user). + Activities should have default user avatar 2. Switch to branch with this feature & migrate data. + Activities from previous GitOps run should use API-only user avatar and have `actor_api_only` flag set to `true`. 3. Run GitOps again. + New activities should use API-only user avatar and have `actor_api_only` flag set to `true`. 4. Give the API-only user a gravatar. Run GitOps again. + Activities should use the configured gravatar. <!-- Consider: Do the steps above apply to all global access roles, including admin, maintainer, observer, observer+, and GitOps? Do the steps above apply to all team-level access roles? If not, write the steps used to test each variation. --> ### Testing notes <!-- Any additional testing notes relevant to this story or tools required for testing. --> ### Confirmation <!-- The engineer responsible for implementing this user story completes the test plan before moving to the "Ready for QA" column. --> 1. [ ] Engineer: Added comment to user story confirming successful completion of test plan. 2. [ ] QA: Added comment to user story confirming successful completion of test plan.
Goal
Key result
Small UX improvements
Original requests
#26921
Context
Changes
Product
Once shipped, dogfooding issue has been filedN/A (small UX improvement)Engineering
QA
Risk assessment
Test plan
actor_api_onlyflag set totrue.actor_api_onlyflag set totrue.Testing notes
Confirmation