You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Purushotham Pushpavanthar (JIRA)" <ji...@apache.org> on 2019/06/23 16:15:00 UTC

[jira] [Updated] (NIFI-6389) Status History panel doesn't retain selected time interval when switched between different metrics

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

Purushotham Pushpavanthar updated NIFI-6389:
--------------------------------------------
    Attachment: Screenshot 2019-06-21 at 3.25.22 PM.png
                Screenshot 2019-06-21 at 3.25.38 PM.png

> Status History panel doesn't retain selected time interval when switched between different metrics 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6389
>                 URL: https://issues.apache.org/jira/browse/NIFI-6389
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>    Affects Versions: 1.9.2
>            Reporter: Purushotham Pushpavanthar
>            Priority: Minor
>              Labels: easyfix, newbie, usability
>         Attachments: Screenshot 2019-06-21 at 3.25.22 PM.png, Screenshot 2019-06-21 at 3.25.38 PM.png
>
>
> The Status History has two charts - one for 24 HR summary and another for details.
> One can select portion of a chart to view its details in detailed chart.
> However when specific portion/time interval is selected on one metric and then switch to another metric the selected portion doesn't apply in the newly selected metric. It will be very convenient if the selected portion is retained when there is a switch.
> I've attached screenshots:
> In the first image I'm interested in *Bytes Transferred* between 9.20 and 10.00 (This is a batch job which runs around this time daily). 
> Where as in second image, when I switch to *FlowFiles Out* metric, the previous selection vanishes. I had to select the region again which is a pain.



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