Project

General

Profile

Actions

Feature #44912

closed

mgr/dashboard: Forms should wait until all data is ready until it is displayed

Added by Tiago Melo about 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
General
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus
Reviewed:
Affected Versions:
Pull request ID:

Description

This was reported in the Ceph Dashboard Octopus roadmap:

Do not display forms until all "inputs" are populated (e.g. dropdowns). Otherwise user will see some "blinkings".


Related issues 3 (0 open3 closed)

Related to Dashboard - Bug #46276: mgr/dashboard: NFS edit form hangs on loadingResolvedTiago Melo

Actions
Has duplicate Dashboard - Cleanup #45146: mgr/dashboard: error and loading panel cleanupDuplicate

Actions
Copied to Dashboard - Backport #45542: octopus: mgr/dashboard: Forms should wait until all data is ready until it is displayedRejectedActions
Actions #1

Updated by Tiago Melo almost 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Tiago Melo
Actions #2

Updated by Tiago Melo almost 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 34746
Actions #3

Updated by Lenz Grimmer almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v16.0.0
  • Backport set to octopus
Actions #4

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #45542: octopus: mgr/dashboard: Forms should wait until all data is ready until it is displayed added
Actions #5

Updated by Tatjana Dehler almost 4 years ago

  • Has duplicate Cleanup #45146: mgr/dashboard: error and loading panel cleanup added
Actions #6

Updated by Lenz Grimmer almost 4 years ago

  • Related to Bug #46276: mgr/dashboard: NFS edit form hangs on loading added
Actions #7

Updated by Lenz Grimmer almost 4 years ago

  • Status changed from Pending Backport to Resolved
  • Backport deleted (octopus)
Actions #8

Updated by Nathan Cutler almost 4 years ago

  • Backport set to octopus

When a backport enters "Rejected" state, the scripts interpret this as a final disposition similar to "Resolved". We need to keep the backport listed in the Backport field in this case. Otherwise someone might think the backport was overlooked and re-add it.

ADDENDUM: the word "Rejected" here means that the very idea that this fix/feature should be backported to Octopus was rejected, not that a specific implementation of the backport was "rejected" (e.g. PR was closed due to some issue with conflict resolution).

Actions #9

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 132 to General
Actions

Also available in: Atom PDF