You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/12/19 15:56:00 UTC

[jira] [Commented] (NIFI-4402) Add component location in Summary view

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

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

Github user pvillard31 commented on the issue:

    https://github.com/apache/nifi/pull/2195
  
    Hey @yuri1969 and @mcgilman - just did a test in a secured env where a user only has access to a specific process group. It LGTM:
    
    <img width="1214" alt="screen shot 2017-12-19 at 4 52 23 pm" src="https://user-images.githubusercontent.com/11541012/34165711-509f4358-e4dd-11e7-8e43-dfad8f667a7f.png">
    
    Does it sound OK to you @mcgilman ?
    Happy to check something else if needed. Thanks!



> Add component location in Summary view
> --------------------------------------
>
>                 Key: NIFI-4402
>                 URL: https://issues.apache.org/jira/browse/NIFI-4402
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>            Reporter: Pierre Villard
>            Priority: Minor
>
> In the summary view, when there are hundreds of processors, it can be difficult to know what exact processor we are looking at in the table. The only options are:
> - go to the processor location to know what processor it is (but then we are not on the summary view anymore)
> - have a naming convention to uniquely name every component
> To improve the user experience, the following could be implemented:
> - add a column "Process Group" displaying the name of the parent process group containing the component
> - when hovering the "Go to location" button change the tooltip to include the path of the component. Something like: "Go to /NiFi Flow/My RPG/My Processor" 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)