Project

General

Profile

Actions

Bug #13352

closed

Dashboard widget rows are loaded in reverse order

Added by Stephen Benjamin about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Dashboard
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

See this on a develop production install on centos7 . Screenshot attached.


Files

dash.png View dash.png 62.2 KB Stephen Benjamin, 01/25/2016 06:17 AM

Related issues 1 (1 open0 closed)

Related to Katello - Bug #13706: Dashboard items are on topNeed more information02/15/2016Actions
Actions #1

Updated by Dominic Cleal about 8 years ago

  • translation missing: en.field_release set to 71

Appears to be a recent regression, looks fine on 1.10.

Actions #2

Updated by Ohad Levy about 8 years ago

  • Related to Bug #13706: Dashboard items are on top added
Actions #3

Updated by Dominic Cleal about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal
Actions #4

Updated by The Foreman Bot about 8 years ago

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

Updated by Dominic Cleal about 8 years ago

Some additional data from an installation suffering from this bug. When rendering the dashboard with a new user's seeded widgets, all rows and cols are 1, but the order of widgets returned from the database is the reverse of what you'd expect:

irb(main):008:0> User.first.widgets
=> #<ActiveRecord::Associations::CollectionProxy [#<Widget id: 12, user_id: 3, template: "distribution_widget", name: "Distribution chart", data: {}, sizex: 6, sizey: 1, col: 1, row: 1, hide: false, created_at: "2016-03-17 11:12:43", updated_at: "2016-03-17 11:12:43">, #<Widget id: 11, user_id: 3, template: "reports_widget", name: "Report summary", data: {}, sizex: 6, sizey: 1, col: 1, row: 1, hide: false, created_at: "2016-03-17 11:12:43", updated_at: "2016-03-17 11:12:43">, #<Widget id: 10, user_id: 3, template: "status_chart_widget", name: "Status chart", data: {}, sizex: 4, sizey: 1, col: 1, row: 1, hide: false, created_at: "2016-03-17 11:12:43", updated_at: "2016-03-17 11:12:43">, #<Widget id: 9, user_id: 3, template: "status_widget", name: "Status table", data: {}, sizex: 8, sizey: 1, col: 1, row: 1, hide: false, created_at: "2016-03-17 11:12:43", updated_at: "2016-03-17 11:12:43">]>

IDs are actually descending, and so the dashboard ends up "backwards", in the opposite order to the default widget registration order.

Actions #6

Updated by Dominic Cleal about 8 years ago

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

Updated by Ohad Levy almost 8 years ago

  • Bugzilla link set to 1325644
Actions

Also available in: Atom PDF