Project

General

Profile

Actions

Bug #16461

closed

Role filter is not overriding from CLI and API

Added by Jitendra Yejare about 8 years ago. Updated over 6 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1373840
Description of problem:
According to new feature Canned Role:Org Admin, The user should be able to override the taxonomies of role filter over role taxonomies.
The behavior is expected from UI, but not from hammer CLI and API. I am unable to override the taxonomies of role filter. The CLI says it does overrided the role filter and API says 200 OK result but the override is not actually happening. In short the results from API and CLI are false positive.

Version-Release number of selected component (if applicable):
foreman-1.13.0-0.develop.201609051301git713be41.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a role with taxonomies.
2. Create/(Update existing) filter in above role with overridden taxonomies from CLI/API.
3. Verify if role filter is created/Updated with taxonomies.

Actual results:
Role filter is not overriding from CLI and API.

Expected results:
The role filter should be able to override from CLI and API.

Additional info:


Related issues 2 (0 open2 closed)

Related to Foreman - Feature #7806: As a user, I would like roles to associate roles with organizations.ClosedMarek Hulán10/03/2014Actions
Related to Foreman - Bug #17107: Expose override attribute in filter API outputClosedMarek Hulán10/26/2016Actions
Actions #1

Updated by Marek Hulán about 8 years ago

  • Category set to Users, Roles and Permissions
Actions #2

Updated by Marek Hulán about 8 years ago

  • Related to Feature #7806: As a user, I would like roles to associate roles with organizations. added
Actions #3

Updated by Marek Hulán about 8 years ago

  • Target version set to 1.5.3
  • Translation missing: en.field_release set to 160

The override flag should be exposed in API, since the feature was introduced in 1.13 I'm aligning this to the same version.

Actions #4

Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3822 added
Actions #5

Updated by Marek Hulán about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #6

Updated by Marek Hulán about 8 years ago

  • Related to Bug #17107: Expose override attribute in filter API output added
Actions

Also available in: Atom PDF