[ 
https://issues.apache.org/jira/browse/NIFI-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530877#comment-15530877
 ] 

ASF GitHub Bot commented on NIFI-1851:
--------------------------------------

GitHub user scottyaslan opened a pull request:

    https://github.com/apache/nifi/pull/1079

    [NIFI-1851] correctly display number of total process groups upon ref…

    …resh

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/scottyaslan/nifi NIFI-1851

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1079.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1079
    
----
commit 0264646353d544f44d8f920317923c6dfaf53930
Author: Scott Aslan <scottyas...@gmail.com>
Date:   2016-09-28T20:47:35Z

    [NIFI-1851] correctly display number of total process groups upon refresh

----


> NiFi summary filter displays wrong number of total results for Process Groups 
> after refresh
> -------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1851
>                 URL: https://issues.apache.org/jira/browse/NIFI-1851
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 0.6.0
>            Reporter: Andrew Lim
>            Assignee: Scott Aslan
>            Priority: Minor
>         Attachments: NIFI-1851_zeroResultsProcessGroup.png
>
>
> Pre-conditions:
> Flow that has multiple process groups
> Steps to Reproduce:
> 1. Go to NiFi Summary Page
> 2. Select Process Groups tab
> 3. Note the numbers displayed next to the Filter ie. Displaying 5 of 5
> 4. Select the "Refresh" icon next to the Process Groups tab
> 5.  The numbers displayed will now be "Displaying x of 0"   (see attached 
> screenshot)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to