Project

General

Custom queries

Profile

Actions
Copy link

Refactor #100

closed

Store Foreman Settings in the database and allow configure it using the WebUI/API

Added by Martin Englund over 15 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ohad Levy
Category:
-
Target version:
0.4
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Provide a mechanism to allow a user to have specific settings associated with them. This will supersede the current SETTINGS hash and allow overriding on a per user, per-model basis.

The idea is that there is a per_page setting at the system level, a per_page setting at the model level for each user and this should also allow for saving things like the user's search history and preferences.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #1159: Class import behaviour not consistent "rake puppet:import:puppet_classes" x "UI"ClosedOhad Levy09/07/2011Actions
#2

Updated by Ohad Levy over 14 years ago

  • Assignee changed from Martin Englund to Paul Kelly
#3

Updated by Paul Kelly about 14 years ago

  • Subject changed from Turn $settings into a Ruby object to Provide a persistent user-specific settings object
#4

Updated by Ohad Levy almost 14 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
#5

Updated by Ohad Levy almost 14 years ago

  • Subject changed from Provide a persistent user-specific settings object to Store Foreman Settings in the database and allow configure it using the WebUI/API
  • Assignee changed from Paul Kelly to Ohad Levy
  • Target version set to 0.4
Actions
Copy link

Also available in: Atom PDF