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

Policies page has incorrect copy for install software automation scope #25062

Closed
jmwatts opened this issue Dec 31, 2024 · 2 comments
Closed

Policies page has incorrect copy for install software automation scope #25062

jmwatts opened this issue Dec 31, 2024 · 2 comments
Assignees
Labels
bug Something isn't working as documented ~frontend Frontend-related issue. #g-mdm MDM product group :incoming New issue in triage process. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~unreleased bug This bug was found in an unreleased version of Fleet.
Milestone

Comments

@jmwatts
Copy link
Member

jmwatts commented Dec 31, 2024

Fleet version: v4.62.0

Web browser and operating system: Chrome 131.0.6778.205 on macOS


πŸ’₯ Β Actual behavior

image
Copy references profiles

πŸ§‘β€πŸ’» Β Steps to reproduce

  1. Create a policy that uses the "Install software" automation. This can be created manually or by adding a new software title and choosing the Automation install method.
  2. On Policies page, click on automatic install policy

πŸ•―οΈ Expected results

Copy is shown below the Target section: "Your policy will only run on the selected platform(s). Additionally, if install software automation is enabled, it will run only on hosts defined in the software scope."

Copy needs to be updated for the new Custom Target scoping feature.

@jmwatts jmwatts added bug Something isn't working as documented :reproduce Involves documenting reproduction steps in the issue :incoming New issue in triage process. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. #g-mdm MDM product group ~unreleased bug This bug was found in an unreleased version of Fleet. and removed :reproduce Involves documenting reproduction steps in the issue labels Dec 31, 2024
@jmwatts jmwatts added this to the 4.62.0-tentative milestone Dec 31, 2024
@ghernandez345 ghernandez345 self-assigned this Jan 2, 2025
@ghernandez345 ghernandez345 added the ~frontend Frontend-related issue. label Jan 2, 2025
ghernandez345 added a commit that referenced this issue Jan 2, 2025
relates to #25062, 25063

quick fixes for UI issues with scoped software via labels feature.

- [x] Manual QA for all new/changed functionality
@jmwatts
Copy link
Member Author

jmwatts commented Jan 7, 2025

QA Notes

This is now fixed on v4.62.0.
Screenshot 2025-01-07 at 1 03 34β€―PM

@fleet-release
Copy link
Contributor

Correct copy in place,
Guides users with grace.
Fleet soars in cyberspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as documented ~frontend Frontend-related issue. #g-mdm MDM product group :incoming New issue in triage process. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~unreleased bug This bug was found in an unreleased version of Fleet.
Development

No branches or pull requests

4 participants