fleet/changes/17048-updating-policy-name
Victor Lyuboslavsky a82fdac8a6
Fixed bug where updating policy name can result with multiple policies with the same name in a team. (#17059)
Fixed bug where updating policy name can result with multiple policies
with the same name in a team.
#17048 
# Checklist for submitter
- [x] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [x] Added/updated tests
- [x] If database migrations are included, checked table schema to
confirm autoupdate
- For database migrations:
- [x] Checked schema for all modified table for columns that will
auto-update timestamps during migration.
- [x] Confirmed that updating the timestamps is acceptable, and will not
cause unwanted side effects.
- [x] Manual QA for all new/changed functionality
2024-02-22 12:13:07 -06:00

2 lines
255 B
Text

Fixed bug where updating policy name can result with multiple policies with the same name in a team.
- This bug was introduced in fleet v4.44.1. Any duplicate policy names in the same team will be renamed by adding a number to the end of the policy name.