-
Notifications
You must be signed in to change notification settings - Fork 450
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
Software title page: add "Last updated" to versions and host counts #22269
Comments
Change is BE only. |
Bumping estimate to 2 as at the very least this needs to be tested end-to-end, and FE functionality will probably need to be enabled to look for the count property. I can handle any small FE bits but don't want to assume that both parts are trivial until I've had a look at the code. |
…#23478) #22269 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Added/updated tests - [x] Manual QA for all new/changed functionality
Verified this locally. |
This user story shipped in Fleet 4.60.0 🚀 @pintomi1989 I can't remember why I added preston to this user story. I removed them b/c I think it was a mistake. Here's the story's feature request: #22222 Preston isn't tagged there^ cc @zayhanlon |
Fresh data on page, |
Goal
Objective
None. Not tied to a quarterly objective.
@noahtalerman: Why are we prioritizing it? Follow up to #19551 which was shipped in 4.57 (see context section below)
Context
During the 4.57 sprint, we decided to push this feature out of the "Policy automations: install software" (#19551) story to move quickly
versions_updated_at
field to support "last updated" UI #22222Changes
Product
Engineering
QA
Risk assessment
Manual testing steps
Confirmation
The text was updated successfully, but these errors were encountered: