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

Software title page: add "Last updated" to versions and host counts #22269

Open
11 of 13 tasks
noahtalerman opened this issue Sep 20, 2024 · 3 comments
Open
11 of 13 tasks
Assignees
Labels
customer-preston #g-endpoint-ops Endpoint ops product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Sep 20, 2024

Goal

User story
As an IT admin looking at the Software title page (ex. Zoom),
I want to know how fresh the version and host counts are
so that I can understand how my Zoom upgrade efforts are going.

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

Changes

Product

  • UI changes: Wireframes are in Figma here
  • CLI (fleetctl) usage changes: No changes.
  • YAML changes: No change.
  • Fleet's agent (fleetd) changes: No changes.
  • Activity changes: No changes.
  • Permissions changes: No changes.
  • Changes to paid features or tiers: No changes.
  • Once shipped, requester has been notified

Engineering

  • REST API changes: Update software title API endpoint
  • Reference documentation changes: Update API reference docs
  • Feature guide changes: No changes

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

  • Requires load testing: No
  • Risk level: Low

Manual testing steps

  1. Sync up a host with software installed
  2. Check the software details page and confirm that an updated-at timestamp is shown, as per Figma

Confirmation

  1. Engineer (@iansltx): Added comment to user story confirming successful completion of QA.
  2. QA (@xpkoala): Added comment to user story confirming successful completion of QA.
@noahtalerman noahtalerman added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) #g-endpoint-ops Endpoint ops product group labels Sep 20, 2024
@noahtalerman noahtalerman self-assigned this Sep 20, 2024
@sharon-fdm
Copy link
Collaborator

Change is BE only.
Estimating 1 since we think we have it. (could be a 2 points as well)

@iansltx
Copy link
Member

iansltx commented Oct 30, 2024

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.

@iansltx iansltx added :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. and removed :product Product Design department (shows up on 🦢 Drafting board) labels Oct 30, 2024
@iansltx iansltx added this to the 4.60.0-tentative milestone Nov 3, 2024
iansltx added a commit that referenced this issue Nov 5, 2024
…#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
@iansltx
Copy link
Member

iansltx commented Nov 8, 2024

Verified this locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-preston #g-endpoint-ops Endpoint ops product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. story A user story defining an entire feature
Development

No branches or pull requests

3 participants