[ 
https://issues.apache.org/jira/browse/METRON-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Meller updated METRON-2103:
---------------------------------
    Description: 
Click through navigation menu has to be configurable.

Currently, configuration stored in a JSON file under
 metron/metron-interface/metron-alerts/src/assets/context-menu.conf.json
 and bundled with the Alerts UI.

As the first iteration probably enough to extend Management UI where user can
 * turn on feature (currently, this feature is turned on by default with the 
default config template)
 * add default config JSON template
 * edit config JSON

As a followup improvement, we could eliminate the JSON on the UI and replace it 
with a form-based solution.

  was:
Click through navigation menu has to be configurable.

Currently, configuration stored in a JSON file under
metron/metron-interface/metron-alerts/src/assets/context-menu.conf.json
and bundled with the Alerts UI.

As the first iteration probably enough to extend Management UI where user can
 * turn on feature
 * add default config JSON template
 * edit config JSON

As a followup improvement, we could eliminate the JSON on the UI and replace it 
with a form-based solution.


> [UI] Impl Click Through navigation admin interface on Management UI
> -------------------------------------------------------------------
>
>                 Key: METRON-2103
>                 URL: https://issues.apache.org/jira/browse/METRON-2103
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Tibor Meller
>            Priority: Major
>
> Click through navigation menu has to be configurable.
> Currently, configuration stored in a JSON file under
>  metron/metron-interface/metron-alerts/src/assets/context-menu.conf.json
>  and bundled with the Alerts UI.
> As the first iteration probably enough to extend Management UI where user can
>  * turn on feature (currently, this feature is turned on by default with the 
> default config template)
>  * add default config JSON template
>  * edit config JSON
> As a followup improvement, we could eliminate the JSON on the UI and replace 
> it with a form-based solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to