[jira] [Resolved] (AMBARI-25099) [Log Search UI] two timezones with the same ID

2019-02-06 Thread Istvan Tobias (JIRA)


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

Istvan Tobias resolved AMBARI-25099.

Resolution: Fixed

> [Log Search UI] two timezones with the same ID
> --
>
> Key: AMBARI-25099
> URL: https://issues.apache.org/jira/browse/AMBARI-25099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 24h
>  Time Spent: 20m
>  Remaining Estimate: 23h 40m
>
> In the time zone selection box the two CST time zones collide: "Central 
> Standard Time" and "China Standard Time" are both abbreviated as CST, and due 
> to this if the user clicks on the CST button, or moves the mouse over any of 
> these regions, then both of them are highlighted.



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


[jira] [Updated] (AMBARI-25147) [Log Search UI] Update the development readme

2019-02-06 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25147:
---
Issue Type: Task  (was: Bug)

> [Log Search UI] Update the development readme
> -
>
> Key: AMBARI-25147
> URL: https://issues.apache.org/jira/browse/AMBARI-25147
> Project: Ambari
>  Issue Type: Task
>  Components: logsearch
>Affects Versions: 2.7.4
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Add UI dev instruction to the development docs.



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


[jira] [Created] (AMBARI-25147) [Log Search UI] Update the development readme

2019-02-06 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25147:
--

 Summary: [Log Search UI] Update the development readme
 Key: AMBARI-25147
 URL: https://issues.apache.org/jira/browse/AMBARI-25147
 Project: Ambari
  Issue Type: Bug
  Components: logsearch
Affects Versions: 2.7.4
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Add UI dev instruction to the development docs.



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


[jira] [Updated] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator

2019-01-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25028:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Populate `Component Name` in validator
> --
>
> Key: AMBARI-25028
> URL: https://issues.apache.org/jira/browse/AMBARI-25028
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 6h
>  Time Spent: 20m
>  Remaining Estimate: 5h 40m
>
> Populate the `component name` field in validator when it is available from 
> the configuration object. 
> If more than component is available populate with the first one.



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


[jira] [Created] (AMBARI-25099) [Log Search UI] two timezones with the same ID

2019-01-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25099:
--

 Summary: [Log Search UI] two timezones with the same ID
 Key: AMBARI-25099
 URL: https://issues.apache.org/jira/browse/AMBARI-25099
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


In the time zone selection box the two CST time zones collide: "Central 
Standard Time" and "China Standard Time" are both abbreviated as CST, and due 
to this if the user clicks on the CST button, or moves the mouse over any of 
these regions, then both of them are highlighted.



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


[jira] [Updated] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator

2019-01-04 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25028:
---
Status: Patch Available  (was: Open)

> [Log Search UI] Populate `Component Name` in validator
> --
>
> Key: AMBARI-25028
> URL: https://issues.apache.org/jira/browse/AMBARI-25028
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 6h
>  Time Spent: 10m
>  Remaining Estimate: 5h 50m
>
> Populate the `component name` field in validator when it is available from 
> the configuration object. 
> If more than component is available populate with the first one.



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


[jira] [Created] (AMBARI-25081) [Log Search UI] Add pagination settings to the user settings

2019-01-03 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25081:
--

 Summary: [Log Search UI] Add pagination settings to the user 
settings
 Key: AMBARI-25081
 URL: https://issues.apache.org/jira/browse/AMBARI-25081
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Add the pagination settings (page size) to the user settings, so that user can 
see the same number of list item every login.



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


[jira] [Updated] (AMBARI-25081) [Log Search UI] Add pagination settings to the user settings

2019-01-03 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25081:
---
Issue Type: Task  (was: Bug)

> [Log Search UI] Add pagination settings to the user settings
> 
>
> Key: AMBARI-25081
> URL: https://issues.apache.org/jira/browse/AMBARI-25081
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Add the pagination settings (page size) to the user settings, so that user 
> can see the same number of list item every login.



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


[jira] [Updated] (AMBARI-25029) [Log Search UI] change the colors of the service links

2019-01-03 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25029:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] change the colors of the service links
> --
>
> Key: AMBARI-25029
> URL: https://issues.apache.org/jira/browse/AMBARI-25029
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>




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


[jira] [Updated] (AMBARI-25029) [Log Search UI] change the colors of the service links

2018-12-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25029:
---
Status: Patch Available  (was: Open)

> [Log Search UI] change the colors of the service links
> --
>
> Key: AMBARI-25029
> URL: https://issues.apache.org/jira/browse/AMBARI-25029
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>




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


[jira] [Created] (AMBARI-25029) [Log Search UI] change the colors of the service links

2018-12-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25029:
--

 Summary: [Log Search UI] change the colors of the service links
 Key: AMBARI-25029
 URL: https://issues.apache.org/jira/browse/AMBARI-25029
 Project: Ambari
  Issue Type: Sub-task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator

2018-12-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25028:
---
  Priority: Minor  (was: Major)
Issue Type: Sub-task  (was: Technical task)

> [Log Search UI] Populate `Component Name` in validator
> --
>
> Key: AMBARI-25028
> URL: https://issues.apache.org/jira/browse/AMBARI-25028
> Project: Ambari
>  Issue Type: Sub-task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Populate the `component name` field in validator when it is available from 
> the configuration object. 
> If more than component is available populate with the first one.



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


[jira] [Created] (AMBARI-25028) [Log Search UI] Populate `Component Name` in validator

2018-12-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25028:
--

 Summary: [Log Search UI] Populate `Component Name` in validator
 Key: AMBARI-25028
 URL: https://issues.apache.org/jira/browse/AMBARI-25028
 Project: Ambari
  Issue Type: Technical task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Populate the `component name` field in validator when it is available from the 
configuration object. 

If more than component is available populate with the first one.



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


[jira] [Created] (AMBARI-25027) [Log Search UI] Small fixes for shipper config page

2018-12-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25027:
--

 Summary: [Log Search UI] Small fixes for shipper config page
 Key: AMBARI-25027
 URL: https://issues.apache.org/jira/browse/AMBARI-25027
 Project: Ambari
  Issue Type: Task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Resolved] (AMBARI-25026) [Log Search UI] Audit log list: missing event time value in the log list

2018-12-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias resolved AMBARI-25026.

Resolution: Fixed

> [Log Search UI] Audit log list: missing event time value in the log list
> 
>
> Key: AMBARI-25026
> URL: https://issues.apache.org/jira/browse/AMBARI-25026
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The value of the event time is not displayed at all in the audit log list.



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


[jira] [Created] (AMBARI-25026) [Log Search UI] Audit log list: missing event time value in the log list

2018-12-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25026:
--

 Summary: [Log Search UI] Audit log list: missing event time value 
in the log list
 Key: AMBARI-25026
 URL: https://issues.apache.org/jira/browse/AMBARI-25026
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


The value of the event time is not displayed at all in the audit log list.



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


[jira] [Updated] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25017:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Replace Log Search favicon with Ambari's favicon
> 
>
> Key: AMBARI-25017
> URL: https://issues.apache.org/jira/browse/AMBARI-25017
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>




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


[jira] [Updated] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24896:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Turn off features in the client when it is not available on 
> backend
> ---
>
> Key: AMBARI-24896
> URL: https://issues.apache.org/jira/browse/AMBARI-24896
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>
> Turn off features when it is not available on backend.
> The list of features and their available status is under `/info/features`.
> Turn off `Configuration Editor` when `metadata_patterns` is `false`.



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


[jira] [Updated] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25015:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Cluster search param added by default when the app loaded on 
> service logs screen
> 
>
> Key: AMBARI-25015
> URL: https://issues.apache.org/jira/browse/AMBARI-25015
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>




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


[jira] [Updated] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25016:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}



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


[jira] [Updated] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25012:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Log Search UI: cannot save filters + select all selecting the ovirrides as 
> well
> ---
>
> Key: AMBARI-25012
> URL: https://issues.apache.org/jira/browse/AMBARI-25012
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Clicking out a log level from debug to nothing, save button was still 
> disabled.
> Also clicking select all selected the overrides rows as well (as no hostname 
> set there or anything, not sure what is expected there, hopefully we would 
> not save that with filled empty hostname but with one debug log level)



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


[jira] [Updated] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25017:
---
Status: Patch Available  (was: Open)

> [Log Search UI] Replace Log Search favicon with Ambari's favicon
> 
>
> Key: AMBARI-25017
> URL: https://issues.apache.org/jira/browse/AMBARI-25017
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>




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


[jira] [Created] (AMBARI-25017) [Log Search UI] Replace Log Search favicon with Ambari's favicon

2018-12-07 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25017:
--

 Summary: [Log Search UI] Replace Log Search favicon with Ambari's 
favicon
 Key: AMBARI-25017
 URL: https://issues.apache.org/jira/browse/AMBARI-25017
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25016:
---
Status: Patch Available  (was: Open)

> [Log Search UI] There is console error about TimeZonePicker initialisation
> --
>
> Key: AMBARI-25016
> URL: https://issues.apache.org/jira/browse/AMBARI-25016
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> There is an error in console when the application is initialising:
> {code:java}
> ERROR TypeError: _co.initMap is not a function{code}



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


[jira] [Updated] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen

2018-12-07 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25015:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Cluster search param added by default when the app loaded on 
> service logs screen
> 
>
> Key: AMBARI-25015
> URL: https://issues.apache.org/jira/browse/AMBARI-25015
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>




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


[jira] [Created] (AMBARI-25016) [Log Search UI] There is console error about TimeZonePicker initialisation

2018-12-07 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25016:
--

 Summary: [Log Search UI] There is console error about 
TimeZonePicker initialisation
 Key: AMBARI-25016
 URL: https://issues.apache.org/jira/browse/AMBARI-25016
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


There is an error in console when the application is initialising:
{code:java}
ERROR TypeError: _co.initMap is not a function{code}



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


[jira] [Created] (AMBARI-25015) [Log Search UI] Cluster search param added by default when the app loaded on service logs screen

2018-12-07 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25015:
--

 Summary: [Log Search UI] Cluster search param added by default 
when the app loaded on service logs screen
 Key: AMBARI-25015
 URL: https://issues.apache.org/jira/browse/AMBARI-25015
 Project: Ambari
  Issue Type: Improvement
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well

2018-12-06 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-25012:
---
Status: Patch Available  (was: Open)

> Log Search UI: cannot save filters + select all selecting the ovirrides as 
> well
> ---
>
> Key: AMBARI-25012
> URL: https://issues.apache.org/jira/browse/AMBARI-25012
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Clicking out a log level from debug to nothing, save button was still 
> disabled.
> Also clicking select all selected the overrides rows as well (as no hostname 
> set there or anything, not sure what is expected there, hopefully we would 
> not save that with filled empty hostname but with one debug log level)



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


[jira] [Created] (AMBARI-25012) Log Search UI: cannot save filters + select all selecting the ovirrides as well

2018-12-06 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25012:
--

 Summary: Log Search UI: cannot save filters + select all selecting 
the ovirrides as well
 Key: AMBARI-25012
 URL: https://issues.apache.org/jira/browse/AMBARI-25012
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Clicking out a log level from debug to nothing, save button was still disabled.

Also clicking select all selected the overrides rows as well (as no hostname 
set there or anything, not sure what is expected there, hopefully we would not 
save that with filled empty hostname but with one debug log level)



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


[jira] [Updated] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend

2018-12-06 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24896:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Turn off features in the client when it is not available on 
> backend
> ---
>
> Key: AMBARI-24896
> URL: https://issues.apache.org/jira/browse/AMBARI-24896
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>
> Turn off features when it is not available on backend.
> The list of features and their available status is under `/info/features`.
> Turn off `Configuration Editor` when `metadata_patterns` is `false`.



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


[jira] [Updated] (AMBARI-23820) [Log Search UI] add different options of hostname display

2018-12-06 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-23820:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] add different options of hostname display
> -
>
> Key: AMBARI-23820
> URL: https://issues.apache.org/jira/browse/AMBARI-23820
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 48h
>  Time Spent: 48h
>  Remaining Estimate: 0h
>
> Provide a setting to show FQDN or short hostname:
> FQDN: logsearch-demo-1.c.pramod-thangali.internal
> Short Hostname: logsearch-demo-1
> If shortname is preferred then show: FQDN.split(“.”)[0]



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


[jira] [Created] (AMBARI-25009) [Log Search UI] Create shared common solution to open application modals.

2018-12-06 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-25009:
--

 Summary: [Log Search UI] Create shared common solution to open 
application modals.
 Key: AMBARI-25009
 URL: https://issues.apache.org/jira/browse/AMBARI-25009
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Create a shared way to open modals available from different components from the 
application.

Currently we have three modals which can be opened from (almost) any point of 
the application:
 * user settings
 * time zone settings
 * log index filter settings

Now the open and close logic are slightly different in each. The goal is to 
have a common way to request open or close state any of these.



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


[jira] [Updated] (AMBARI-23820) [Log Search UI] add different options of hostname display

2018-12-05 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-23820:
---
Status: Patch Available  (was: Open)

> [Log Search UI] add different options of hostname display
> -
>
> Key: AMBARI-23820
> URL: https://issues.apache.org/jira/browse/AMBARI-23820
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 48h
>  Time Spent: 48h
>  Remaining Estimate: 0h
>
> Provide a setting to show FQDN or short hostname:
> FQDN: logsearch-demo-1.c.pramod-thangali.internal
> Short Hostname: logsearch-demo-1
> If shortname is preferred then show: FQDN.split(“.”)[0]



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


[jira] [Updated] (AMBARI-24975) Log Search UI: if there are multiple clusters - selecting one of it does not do anything

2018-11-30 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24975:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Log Search UI: if there are multiple clusters - selecting one of it does not 
> do anything
> 
>
> Key: AMBARI-24975
> URL: https://issues.apache.org/jira/browse/AMBARI-24975
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When there is more then one clusters, if im selecting one, service log tabs / 
> graphs are not changing at all. also im not seeing cluster field in the url 
> hash
> expectation: it should resend the queries



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


[jira] [Updated] (AMBARI-24975) Log Search UI: if there are multiple clusters - selecting one of it does not do anything

2018-11-30 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24975:
---
Status: Patch Available  (was: In Progress)

> Log Search UI: if there are multiple clusters - selecting one of it does not 
> do anything
> 
>
> Key: AMBARI-24975
> URL: https://issues.apache.org/jira/browse/AMBARI-24975
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When there is more then one clusters, if im selecting one, service log tabs / 
> graphs are not changing at all. also im not seeing cluster field in the url 
> hash
> expectation: it should resend the queries



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


[jira] [Updated] (AMBARI-24880) [Log Search UI] Create new layout for the Audit log list.

2018-11-30 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24880:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Create new layout for the Audit log list.
> -
>
> Key: AMBARI-24880
> URL: https://issues.apache.org/jira/browse/AMBARI-24880
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>




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


[jira] [Created] (AMBARI-24975) Log Search UI: if there are multiple clusters - selecting one of it does not do anything

2018-11-30 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24975:
--

 Summary: Log Search UI: if there are multiple clusters - selecting 
one of it does not do anything
 Key: AMBARI-24975
 URL: https://issues.apache.org/jira/browse/AMBARI-24975
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


When there is more then one clusters, if im selecting one, service log tabs / 
graphs are not changing at all. also im not seeing cluster field in the url hash

expectation: it should resend the queries



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


[jira] [Updated] (AMBARI-24900) [Log Search UI] Display the number of selection for the multiple selection dropdowns

2018-11-29 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24900:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Display the number of selection for the multiple selection 
> dropdowns
> 
>
> Key: AMBARI-24900
> URL: https://issues.apache.org/jira/browse/AMBARI-24900
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>




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


[jira] [Updated] (AMBARI-24880) [Log Search UI] Create new layout for the Audit log list.

2018-11-28 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24880:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Create new layout for the Audit log list.
> -
>
> Key: AMBARI-24880
> URL: https://issues.apache.org/jira/browse/AMBARI-24880
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>




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


[jira] [Updated] (AMBARI-24900) [Log Search UI] Display the number of selection for the multiple selection dropdowns

2018-11-26 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24900:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Display the number of selection for the multiple selection 
> dropdowns
> 
>
> Key: AMBARI-24900
> URL: https://issues.apache.org/jira/browse/AMBARI-24900
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>




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


[jira] [Resolved] (AMBARI-24882) [Log Search UI] Change sticky filter panel solution from JS to clean css.

2018-11-23 Thread Istvan Tobias (JIRA)


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

Istvan Tobias resolved AMBARI-24882.

Resolution: Fixed

> [Log Search UI] Change sticky filter panel solution from JS to clean css.
> -
>
> Key: AMBARI-24882
> URL: https://issues.apache.org/jira/browse/AMBARI-24882
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>
> Instead of listening scroll event we can use `sticky` css `position`. It is 
> not supported by all the browsers (IE does not support). This does not break 
> functionality but improve performance.



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


[jira] [Resolved] (AMBARI-24945) [Log Search UI] Handling null or undefined value in log's level property.

2018-11-23 Thread Istvan Tobias (JIRA)


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

Istvan Tobias resolved AMBARI-24945.

Resolution: Fixed

> [Log Search UI] Handling null or undefined value in log's level property.
> -
>
> Key: AMBARI-24945
> URL: https://issues.apache.org/jira/browse/AMBARI-24945
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Critical
>  Labels: pull-request-available
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>




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


[jira] [Created] (AMBARI-24945) [Log Search UI] Handling null or undefined value in log's level property.

2018-11-22 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24945:
--

 Summary: [Log Search UI] Handling null or undefined value in log's 
level property.
 Key: AMBARI-24945
 URL: https://issues.apache.org/jira/browse/AMBARI-24945
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-24899) [Log Search UI] Change capture countdown text

2018-11-16 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24899:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Change capture countdown text
> -
>
> Key: AMBARI-24899
> URL: https://issues.apache.org/jira/browse/AMBARI-24899
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The text should be: "Please wait while the logs for your capture period are 
> indexed..."



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


[jira] [Updated] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work

2018-11-16 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24891:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Serach UI] The Log Index Filter panel does not work
> 
>
> Key: AMBARI-24891
> URL: https://issues.apache.org/jira/browse/AMBARI-24891
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>
> The Log Index Filter settings modal does not load the configuration.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-11-15 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 4h
>  Time Spent: 3h 40m
>  Remaining Estimate: 20m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-11-15 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 4h
>  Time Spent: 3h 40m
>  Remaining Estimate: 20m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Created] (AMBARI-24900) [Log Search UI] Display the number of selection for the multiple selection dropdowns

2018-11-14 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24900:
--

 Summary: [Log Search UI] Display the number of selection for the 
multiple selection dropdowns
 Key: AMBARI-24900
 URL: https://issues.apache.org/jira/browse/AMBARI-24900
 Project: Ambari
  Issue Type: Task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-24899) [Log Search UI] Change capture countdown text

2018-11-14 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24899:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Change capture countdown text
> -
>
> Key: AMBARI-24899
> URL: https://issues.apache.org/jira/browse/AMBARI-24899
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The text should be: "Please wait while the logs for your capture period are 
> indexed..."



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


[jira] [Created] (AMBARI-24899) [Log Search UI] Change capture countdown text

2018-11-14 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24899:
--

 Summary: [Log Search UI] Change capture countdown text
 Key: AMBARI-24899
 URL: https://issues.apache.org/jira/browse/AMBARI-24899
 Project: Ambari
  Issue Type: Task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


The text should be: "Please wait while the logs for your capture period are 
indexed..."



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


[jira] [Updated] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work

2018-11-14 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24891:
---
Status: Patch Available  (was: Open)

> [Log Serach UI] The Log Index Filter panel does not work
> 
>
> Key: AMBARI-24891
> URL: https://issues.apache.org/jira/browse/AMBARI-24891
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
>
> The Log Index Filter settings modal does not load the configuration.



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


[jira] [Created] (AMBARI-24896) [Log Search UI] Turn off features in the client when it is not available on backend

2018-11-14 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24896:
--

 Summary: [Log Search UI] Turn off features in the client when it 
is not available on backend
 Key: AMBARI-24896
 URL: https://issues.apache.org/jira/browse/AMBARI-24896
 Project: Ambari
  Issue Type: Task
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Turn off features when it is not available on backend.

The list of features and their available status is under `/info/features`.

Turn off `Configuration Editor` when `metadata_patterns` is `false`.



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


[jira] [Created] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work

2018-11-13 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24891:
--

 Summary: [Log Serach UI] The Log Index Filter panel does not work
 Key: AMBARI-24891
 URL: https://issues.apache.org/jira/browse/AMBARI-24891
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias


The Log Index Filter settings modal does not load the configuration.



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


[jira] [Updated] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item

2018-11-13 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24887:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] The component filter dropdown does not select any item
> --
>
> Key: AMBARI-24887
> URL: https://issues.apache.org/jira/browse/AMBARI-24887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.3
>
>   Original Estimate: 4h
>  Time Spent: 0.5h
>  Remaining Estimate: 3.5h
>
> The user can not select any components from the component filter dropdown.



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


[jira] [Updated] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item

2018-11-13 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24887:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] The component filter dropdown does not select any item
> --
>
> Key: AMBARI-24887
> URL: https://issues.apache.org/jira/browse/AMBARI-24887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.3
>
>   Original Estimate: 4h
>  Time Spent: 20m
>  Remaining Estimate: 3h 40m
>
> The user can not select any components from the component filter dropdown.



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


[jira] [Created] (AMBARI-24887) [Log Search UI] The component filter dropdown does not select any item

2018-11-13 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24887:
--

 Summary: [Log Search UI] The component filter dropdown does not 
select any item
 Key: AMBARI-24887
 URL: https://issues.apache.org/jira/browse/AMBARI-24887
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.3
Reporter: Istvan Tobias
Assignee: Istvan Tobias
 Fix For: 2.7.3


The user can not select any components from the component filter dropdown.



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


[jira] [Created] (AMBARI-24882) [Log Search UI] Change sticky filter panel solution from JS to clean css.

2018-11-12 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24882:
--

 Summary: [Log Search UI] Change sticky filter panel solution from 
JS to clean css.
 Key: AMBARI-24882
 URL: https://issues.apache.org/jira/browse/AMBARI-24882
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Instead of listening scroll event we can use `sticky` css `position`. It is not 
supported by all the browsers (IE does not support). This does not break 
functionality but improve performance.



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


[jira] [Updated] (AMBARI-24880) [Log Search UI] Create new layout for the Audit log list.

2018-11-12 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24880:
---
Remaining Estimate: 72h  (was: 48h)
 Original Estimate: 72h  (was: 48h)
Issue Type: Task  (was: Improvement)

> [Log Search UI] Create new layout for the Audit log list.
> -
>
> Key: AMBARI-24880
> URL: https://issues.apache.org/jira/browse/AMBARI-24880
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>




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


[jira] [Created] (AMBARI-24880) [Log Search UI] Create new layout for the Audit log list.

2018-11-12 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24880:
--

 Summary: [Log Search UI] Create new layout for the Audit log list.
 Key: AMBARI-24880
 URL: https://issues.apache.org/jira/browse/AMBARI-24880
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-23820) [Log Search UI] add different options of hostname display

2018-10-24 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-23820:
---
Fix Version/s: (was: 2.7.3)

> [Log Search UI] add different options of hostname display
> -
>
> Key: AMBARI-23820
> URL: https://issues.apache.org/jira/browse/AMBARI-23820
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 48h
>  Time Spent: 48h
>  Remaining Estimate: 0h
>
> Provide a setting to show FQDN or short hostname:
> FQDN: logsearch-demo-1.c.pramod-thangali.internal
> Short Hostname: logsearch-demo-1
> If shortname is preferred then show: FQDN.split(“.”)[0]



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-10-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Status: Open  (was: Patch Available)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 4h
>  Time Spent: 2h 50m
>  Remaining Estimate: 1h 10m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 4h
>  Time Spent: 2h 40m
>  Remaining Estimate: 1h 20m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Status: Open  (was: Patch Available)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 4h
>  Time Spent: 2h 40m
>  Remaining Estimate: 1h 20m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24613:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Already fixed in apache/ambari-logsearch.

> [Log Search UI] Date picker preset ranges are not displayed properly
> 
>
> Key: AMBARI-24613
> URL: https://issues.apache.org/jira/browse/AMBARI-24613
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> [Logsearch UI] Date picker preset ranges are not displayed properly



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


[jira] [Updated] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24610:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Show user friendly component name in query input
> 
>
> Key: AMBARI-24610
> URL: https://issues.apache.org/jira/browse/AMBARI-24610
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 3h
>  Time Spent: 1h 10m
>  Remaining Estimate: 1h 50m
>




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


[jira] [Updated] (AMBARI-24656) [Log Search UI] Handle the 401 and the 403 response status at login

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24656:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Handle the 401 and the 403 response status at login
> ---
>
> Key: AMBARI-24656
> URL: https://issues.apache.org/jira/browse/AMBARI-24656
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Since the backend response at login/authorisation has been changed in the way 
> that the 401 and the 403 status is handled differently the UI should reflect 
> on this change.



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


[jira] [Updated] (AMBARI-24631) [Log Search UI] styles and layout fixes

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24631:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] styles and layout fixes
> ---
>
> Key: AMBARI-24631
> URL: https://issues.apache.org/jira/browse/AMBARI-24631
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 24h
>  Time Spent: 50h 10m
>  Remaining Estimate: 0h
>
> # Move number of events up on the page higher so it’s centered between the 
> top of the gray area and the beginning of the Histogram frame
>  # The message about triggering auto-refresh should be displayed in modal 
> dialog
>  # Filters panel should be a bit less transparent



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


[jira] [Updated] (AMBARI-24580) [Log Search UI] Change the fix width and the height for the modal to flexible layout

2018-10-08 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24580:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Change the fix width and the height for the modal to flexible 
> layout
> 
>
> Key: AMBARI-24580
> URL: https://issues.apache.org/jira/browse/AMBARI-24580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 48h
>  Time Spent: 50h 20m
>  Remaining Estimate: 0h
>
> The modals have fixed with and height and it can make the app difficult to 
> use. So the modals should be flexible enough to be visible everytime.



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


[jira] [Updated] (AMBARI-24656) [Log Search UI] Handle the 401 and the 403 response status at login

2018-10-04 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24656:
---
Priority: Major  (was: Minor)

> [Log Search UI] Handle the 401 and the 403 response status at login
> ---
>
> Key: AMBARI-24656
> URL: https://issues.apache.org/jira/browse/AMBARI-24656
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Since the backend response at login/authorisation has been changed in the way 
> that the 401 and the 403 status is handled differently the UI should reflect 
> on this change.



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


[jira] [Updated] (AMBARI-24656) [Log Search UI] Handle the 401 and the 403 response status at login

2018-10-04 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24656:
---
Issue Type: Task  (was: Improvement)

> [Log Search UI] Handle the 401 and the 403 response status at login
> ---
>
> Key: AMBARI-24656
> URL: https://issues.apache.org/jira/browse/AMBARI-24656
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Since the backend response at login/authorisation has been changed in the way 
> that the 401 and the 403 status is handled differently the UI should reflect 
> on this change.



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


[jira] [Updated] (AMBARI-24656) [Log Search UI] Handle the 401 and the 403 response status at login

2018-10-04 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24656:
---
Fix Version/s: 2.8.0
   Status: Patch Available  (was: In Progress)

> [Log Search UI] Handle the 401 and the 403 response status at login
> ---
>
> Key: AMBARI-24656
> URL: https://issues.apache.org/jira/browse/AMBARI-24656
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.8.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Since the backend response at login/authorisation has been changed in the way 
> that the 401 and the 403 status is handled differently the UI should reflect 
> on this change.



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


[jira] [Created] (AMBARI-24656) [Log Search UI] Handle the 401 and the 403 response status at login

2018-09-18 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24656:
--

 Summary: [Log Search UI] Handle the 401 and the 403 response 
status at login
 Key: AMBARI-24656
 URL: https://issues.apache.org/jira/browse/AMBARI-24656
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.1
Reporter: Istvan Tobias
Assignee: Istvan Tobias


Since the backend response at login/authorisation has been changed in the way 
that the 401 and the 403 status is handled differently the UI should reflect on 
this change.



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


[jira] [Updated] (AMBARI-24631) [Log Search UI] styles and layout fixes

2018-09-18 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24631:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] styles and layout fixes
> ---
>
> Key: AMBARI-24631
> URL: https://issues.apache.org/jira/browse/AMBARI-24631
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 24h
>  Time Spent: 20m
>  Remaining Estimate: 23h 40m
>
> # Move number of events up on the page higher so it’s centered between the 
> top of the gray area and the beginning of the Histogram frame
>  # The message about triggering auto-refresh should be displayed in modal 
> dialog
>  # Filters panel should be a bit less transparent



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


[jira] [Created] (AMBARI-24631) [Log Search UI] styles and layout fixes

2018-09-12 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24631:
--

 Summary: [Log Search UI] styles and layout fixes
 Key: AMBARI-24631
 URL: https://issues.apache.org/jira/browse/AMBARI-24631
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.0
Reporter: Istvan Tobias
Assignee: Istvan Tobias
 Fix For: 2.7.2


# Move number of events up on the page higher so it’s centered between the top 
of the gray area and the beginning of the Histogram frame
 # The message about triggering auto-refresh should be displayed in modal dialog
 # Filters panel should be a bit less transparent



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


[jira] [Updated] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly

2018-09-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24613:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Date picker preset ranges are not displayed properly
> 
>
> Key: AMBARI-24613
> URL: https://issues.apache.org/jira/browse/AMBARI-24613
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 20m
>  Remaining Estimate: 40m
>
> [Logsearch UI] Date picker preset ranges are not displayed properly



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


[jira] [Created] (AMBARI-24613) [Log Search UI] Date picker preset ranges are not displayed properly

2018-09-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24613:
--

 Summary: [Log Search UI] Date picker preset ranges are not 
displayed properly
 Key: AMBARI-24613
 URL: https://issues.apache.org/jira/browse/AMBARI-24613
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.0
Reporter: Istvan Tobias
Assignee: Istvan Tobias


[Logsearch UI] Date picker preset ranges are not displayed properly



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


[jira] [Updated] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input

2018-09-10 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24610:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Show user friendly component name in query input
> 
>
> Key: AMBARI-24610
> URL: https://issues.apache.org/jira/browse/AMBARI-24610
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 3h
>  Time Spent: 20m
>  Remaining Estimate: 2h 40m
>




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


[jira] [Created] (AMBARI-24610) [Log Search UI] Show user friendly component name in query input

2018-09-10 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24610:
--

 Summary: [Log Search UI] Show user friendly component name in 
query input
 Key: AMBARI-24610
 URL: https://issues.apache.org/jira/browse/AMBARI-24610
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.0
Reporter: Istvan Tobias
Assignee: Istvan Tobias






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


[jira] [Updated] (AMBARI-24580) [Log Search UI] Change the fix width and the height for the modal to flexible layout

2018-09-05 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24580:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Change the fix width and the height for the modal to flexible 
> layout
> 
>
> Key: AMBARI-24580
> URL: https://issues.apache.org/jira/browse/AMBARI-24580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
>   Original Estimate: 48h
>  Time Spent: 10m
>  Remaining Estimate: 47h 50m
>
> The modals have fixed with and height and it can make the app difficult to 
> use. So the modals should be flexible enough to be visible everytime.



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


[jira] [Updated] (AMBARI-24580) [Log Search UI] Change the fix width and the height for the modal to flexible layout

2018-09-05 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24580:
---
Summary: [Log Search UI] Change the fix width and the height for the modal 
to flexible layout  (was: [Log Search UI] Change the fix with and the height 
for the modal to flexible layout)

> [Log Search UI] Change the fix width and the height for the modal to flexible 
> layout
> 
>
> Key: AMBARI-24580
> URL: https://issues.apache.org/jira/browse/AMBARI-24580
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The modals have fixed with and height and it can make the app difficult to 
> use. So the modals should be flexible enough to be visible everytime.



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


[jira] [Created] (AMBARI-24580) [Log Search UI] Change the fix with and the height for the modal to flexible layout

2018-08-31 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24580:
--

 Summary: [Log Search UI] Change the fix with and the height for 
the modal to flexible layout
 Key: AMBARI-24580
 URL: https://issues.apache.org/jira/browse/AMBARI-24580
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.0
Reporter: Istvan Tobias
Assignee: Istvan Tobias


The modals have fixed with and height and it can make the app difficult to use. 
So the modals should be flexible enough to be visible everytime.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-08-28 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 4h
>  Time Spent: 2h 20m
>  Remaining Estimate: 1h 40m
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-08-28 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24551:
---
Fix Version/s: 2.7.2

> [Log Search UI] get rid of redundant requests after undoing or redoing 
> several history steps
> 
>
> Key: AMBARI-24551
> URL: https://issues.apache.org/jira/browse/AMBARI-24551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.1
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
> Fix For: 2.7.2
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> After undoing or redoing more than one history items several redundant API 
> requests are sent. This occurs because changes for several filter controls 
> are applied step-by-step, and each control change generates new request.



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


[jira] [Created] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps

2018-08-28 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24551:
--

 Summary: [Log Search UI] get rid of redundant requests after 
undoing or redoing several history steps
 Key: AMBARI-24551
 URL: https://issues.apache.org/jira/browse/AMBARI-24551
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.1
Reporter: Istvan Tobias
Assignee: Istvan Tobias


After undoing or redoing more than one history items several redundant API 
requests are sent. This occurs because changes for several filter controls are 
applied step-by-step, and each control change generates new request.



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


[jira] [Updated] (AMBARI-24426) [Log Search UI] Show user friendly component names in Log Index Filter screen

2018-08-27 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24426:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Show user friendly component names in Log Index Filter screen
> -
>
> Key: AMBARI-24426
> URL: https://issues.apache.org/jira/browse/AMBARI-24426
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 6h
>  Time Spent: 50m
>  Remaining Estimate: 5h 10m
>
> Show the user friendly component names on the screen of the Log Index Filter, 
> where the filter level can be set up.



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


[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover

2018-08-27 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24435:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Remove underline text decoration from dropdowns on hover
> 
>
> Key: AMBARI-24435
> URL: https://issues.apache.org/jira/browse/AMBARI-24435
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 2h
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> The dropdown buttons have underline text decoration on mouse hover, it should 
> be removed.



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


[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover

2018-08-27 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24435:
---
Fix Version/s: 2.7.2

> [Log Search UI] Remove underline text decoration from dropdowns on hover
> 
>
> Key: AMBARI-24435
> URL: https://issues.apache.org/jira/browse/AMBARI-24435
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 2h
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> The dropdown buttons have underline text decoration on mouse hover, it should 
> be removed.



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


[jira] [Updated] (AMBARI-24426) [Log Search UI] Show user friendly component names in Log Index Filter screen

2018-08-24 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24426:
---
Status: Patch Available  (was: Open)

> [Log Search UI] Show user friendly component names in Log Index Filter screen
> -
>
> Key: AMBARI-24426
> URL: https://issues.apache.org/jira/browse/AMBARI-24426
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.7.2
>
>   Original Estimate: 6h
>  Time Spent: 40m
>  Remaining Estimate: 5h 20m
>
> Show the user friendly component names on the screen of the Log Index Filter, 
> where the filter level can be set up.



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


[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover

2018-08-21 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24435:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Remove underline text decoration from dropdowns on hover
> 
>
> Key: AMBARI-24435
> URL: https://issues.apache.org/jira/browse/AMBARI-24435
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 2h
>  Time Spent: 20m
>  Remaining Estimate: 1h 40m
>
> The dropdown buttons have underline text decoration on mouse hover, it should 
> be removed.



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


[jira] [Updated] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-20 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24490:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Time Histogram Chart keep invert grey selection area when no 
> selection happened
> ---
>
> Key: AMBARI-24490
> URL: https://issues.apache.org/jira/browse/AMBARI-24490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> When the use clicks on the histogram, but he/she does not create selection 
> the grey invert-selection area stays there.



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


[jira] [Updated] (AMBARI-24437) [Log Search UI] App Loader Page - add more space above the loader animations

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24437:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] App Loader Page - add more space above the loader animations
> 
>
> Key: AMBARI-24437
> URL: https://issues.apache.org/jira/browse/AMBARI-24437
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Add space above the loader animations to be more separated from the top.



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


[jira] [Updated] (AMBARI-24436) [Log Search UI] App Loader Page - Align the logo left

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24436:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] App Loader Page - Align the logo left
> -
>
> Key: AMBARI-24436
> URL: https://issues.apache.org/jira/browse/AMBARI-24436
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
> Fix For: 2.7.1
>
>   Original Estimate: 1h
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Align left the logo on the application loader page.



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


[jira] [Reopened] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias reopened AMBARI-24490:


> [Log Search UI] Time Histogram Chart keep invert grey selection area when no 
> selection happened
> ---
>
> Key: AMBARI-24490
> URL: https://issues.apache.org/jira/browse/AMBARI-24490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> When the use clicks on the histogram, but he/she does not create selection 
> the grey invert-selection area stays there.



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


[jira] [Updated] (AMBARI-24433) [Log Search UI] Reset to default selection in the dropdowns

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24433:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Reset to default selection in the dropdowns
> ---
>
> Key: AMBARI-24433
> URL: https://issues.apache.org/jira/browse/AMBARI-24433
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 6h
>  Time Spent: 1h 10m
>  Remaining Estimate: 4h 50m
>
> Table list column selection: create an action button to reset the selection 
> to the default.



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


[jira] [Updated] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24490:
---
Status: Patch Available  (was: Reopened)

> [Log Search UI] Time Histogram Chart keep invert grey selection area when no 
> selection happened
> ---
>
> Key: AMBARI-24490
> URL: https://issues.apache.org/jira/browse/AMBARI-24490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> When the use clicks on the histogram, but he/she does not create selection 
> the grey invert-selection area stays there.



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


[jira] [Updated] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-17 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24490:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] Time Histogram Chart keep invert grey selection area when no 
> selection happened
> ---
>
> Key: AMBARI-24490
> URL: https://issues.apache.org/jira/browse/AMBARI-24490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> When the use clicks on the histogram, but he/she does not create selection 
> the grey invert-selection area stays there.



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


[jira] [Updated] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-16 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24490:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Time Histogram Chart keep invert grey selection area when no 
> selection happened
> ---
>
> Key: AMBARI-24490
> URL: https://issues.apache.org/jira/browse/AMBARI-24490
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 20m
>  Remaining Estimate: 40m
>
> When the use clicks on the histogram, but he/she does not create selection 
> the grey invert-selection area stays there.



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


[jira] [Created] (AMBARI-24490) [Log Search UI] Time Histogram Chart keep invert grey selection area when no selection happened

2018-08-16 Thread Istvan Tobias (JIRA)
Istvan Tobias created AMBARI-24490:
--

 Summary: [Log Search UI] Time Histogram Chart keep invert grey 
selection area when no selection happened
 Key: AMBARI-24490
 URL: https://issues.apache.org/jira/browse/AMBARI-24490
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch, logsearch
Affects Versions: 2.7.0
Reporter: Istvan Tobias
Assignee: Istvan Tobias


When the use clicks on the histogram, but he/she does not create selection the 
grey invert-selection area stays there.



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


[jira] [Updated] (AMBARI-24433) [Log Search UI] Reset to default selection in the dropdowns

2018-08-16 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24433:
---
Status: Patch Available  (was: In Progress)

> [Log Search UI] Reset to default selection in the dropdowns
> ---
>
> Key: AMBARI-24433
> URL: https://issues.apache.org/jira/browse/AMBARI-24433
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 6h
>  Time Spent: 20m
>  Remaining Estimate: 5h 40m
>
> Table list column selection: create an action button to reset the selection 
> to the default.



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


[jira] [Updated] (AMBARI-24438) [Log Search UI] App Loader Page - add initial progress state

2018-08-15 Thread Istvan Tobias (JIRA)


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

Istvan Tobias updated AMBARI-24438:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Log Search UI] App Loader Page - add initial progress state
> 
>
> Key: AMBARI-24438
> URL: https://issues.apache.org/jira/browse/AMBARI-24438
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.0
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 1h
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add some initial progress state to the app loader progress bar:
>  * initial x% value
>  * indeterminate progress bar



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


  1   2   3   >