Make non-dashboard pages part of grafana fork codebase (migration)
General
Escalation
General
Escalation
Description
User story:
As a User I want to be able to navigate through PMM pages (ex: Settings, Inventory, STT Checks, DBaaS, etc) via a non-dashboard interface since that one is distracting and features UI elements irrelevant to the functionality (ex: refresh intervals).
UI/UX:
Acceptance criteria:
All pages unrelated to dashboards are migrated to grafana codebase and have a look a feel similar to that of grafana.
Out of scope:
QAN ???, since it needs a refresh interval
Suggested implementation:
migrate pages one-by-one
selectively port the shared component, keeping them to a necessary minimum
How to test:
Test and assert that the functionality did not degrade after migration All unit tests pass All integration tests pass
User story:
As a User I want to be able to navigate through PMM pages (ex: Settings, Inventory, STT Checks, DBaaS, etc) via a non-dashboard interface since that one is distracting and features UI elements irrelevant to the functionality (ex: refresh intervals).
UI/UX:
Acceptance criteria:
All pages unrelated to dashboards are migrated to grafana codebase and have a look a feel similar to that of grafana.
Out of scope:
QAN ???, since it needs a refresh interval
Suggested implementation:
migrate pages one-by-one
selectively port the shared component, keeping them to a necessary minimum
How to test:
Test and assert that the functionality did not degrade after migration
All unit tests pass
All integration tests pass
Details:
Import what is agreed upon from https://docs.google.com/document/d/1C5epZR5hxfwbF_Ro1hk8o1LXP9g-4AchTZpedqVZq3o/edit