Project

General

Profile

Feature #44912

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

Added by Tiago Melo 10 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/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

Related to mgr - Bug #46276: mgr/dashboard: NFS edit form hangs on loading Resolved
Duplicated by mgr - Cleanup #45146: mgr/dashboard: error and loading panel cleanup Duplicate
Copied to mgr - Backport #45542: octopus: mgr/dashboard: Forms should wait until all data is ready until it is displayed Rejected

History

#1 Updated by Tiago Melo 9 months ago

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

#2 Updated by Tiago Melo 9 months ago

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

#3 Updated by Lenz Grimmer 9 months ago

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

#4 Updated by Nathan Cutler 8 months ago

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

#5 Updated by Tatjana Dehler 7 months ago

  • Duplicated by Cleanup #45146: mgr/dashboard: error and loading panel cleanup added

#6 Updated by Lenz Grimmer 7 months ago

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

#7 Updated by Lenz Grimmer 7 months ago

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

#8 Updated by Nathan Cutler 7 months 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).

Also available in: Atom PDF