Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-2071

Improved navigation system within frontend

XMLWordPrintable

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 2.2.1
    • Frontend (F)
    • None

      Hi,

      The current way to navigate through frontend highly depends on sessions/cookies (even sessions added within GET params, ugly, like in 1990 ages) instead of URL's. This has several big downsides:
      1. Is very hard to impossible to do things like trying to work at same time in two browser tabs at two hosts/templates. Because of the way the navigation is handled you cant actually work at two things at same time.
      2. Hard to understand where you are from URL and passing to co-worker a link is as well messy
      3. No user/seo like friendly URL's

      And there are couple (not one) cookies stored for session like data as I pointed into other bug report.

      Normally all the apps are relying on URL's for navigation and session part is only kept for storing auth part + user data. Not for navigation.

      I have used a lot Zabbix and I think this is the most ancient and totally non-modern part of the frontend.

            Unassigned Unassigned
            cbichis Cristian
            Votes:
            5 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: