Project

General

Profile

Actions

Bug #5122

closed

Default location should not scope anything by default

Added by Ivan Necas almost 10 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Locations are cool feature but they cause more harm than benefit when
the user doesn't explicitly need the feature.

Creating the location with:

  • All users
  • All smart proxies
  • All subnets
  • All compute resources
  • All media
  • All templates
  • All domains
  • All realms
  • All environments
  • All host groups

Should take the locations out of the success path for deployments that don't explicitly need the location stuff.
The user can change that later once they realize they can't live without it

Actions #1

Updated by Ivan Necas almost 10 years ago

  • Description updated (diff)
Actions #2

Updated by Eric Helms almost 10 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 114
Actions #4

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions

Also available in: Atom PDF