Project

General

Profile

Actions

Bug #21545

closed

Role cloning treats taxonomies differently in UI and API

Added by Ondřej Pražák over 6 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Users, Roles and Permissions
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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

Steps to Reproduce:
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
  1. 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.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #32026: Saving invalid cloned role ends up with Internal server errorClosedOndřej EzrActions
Actions

Also available in: Atom PDF