Actions
Bug #21545
closedRole cloning treats taxonomies differently in UI and API
Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Description
Description of problem:
From Hammer CLI, if you clone a role that has taxonomies, then after cloning the same taxonomies are copied over to the cloned role. When clonning in UI, the taxonomies are not selected by default, so role is clonned without taxonomies. We should unify the behaviour.
How reproducible:
Always
1. Create a role with org A and location A
2. Clone above role from hammer CLI without providing any org and location id's
- hammer role clone --id 45 --new-name clied_cloned
3. Clone the same role from UI - just click 'clone' and submit without making any custom changes.
Actual results:
The cloned role using Hammer has taxonomies copied from its parent role while role clonned in UI has no taxonomies.
Expected results:
Cloned role should have same taxonomies regardless of whe way they are clonned.
Updated by Ondřej Pražák over 7 years ago
- Subject changed from Role cloning treats taxonomies differently in UI and API to Role cloning treats taxonomies differently in UI and API
- Category set to 218
- Target version set to 115
Updated by Dominik Hlavac Duran over 6 years ago
- Assignee set to Dominik Hlavac Duran
- Triaged set to No
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6181 added
Updated by Dominik Hlavac Duran about 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset e61362d1a103b4fbd79c838a6bb6f01986ab02a9.
Updated by Tomer Brisker over 4 years ago
- Category changed from 218 to Users, Roles and Permissions
Updated by Ondřej Ezr almost 4 years ago
- Related to Bug #32026: Saving invalid cloned role ends up with Internal server error added
Actions