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

Andrew Lim updated NIFI-2272:
-----------------------------
    Description: 
I reloaded my NiFi instance and selected "Policies" from the control drop-down 
menu.  As shown in the attached screenshot, for the "access the user interface" 
policy, the view/modify drop-down is available.

If you switch to another policy like "query provenance" which correctly doesn't 
have the view/modify drop-down, then if you go back to "access the user 
interface" policy the view/modify drop-down is now gone.

  was:
I reloaded my NiFi instance and selected "Profiles" from the control drop-down 
menu.  As shown in the attached screenshot, for the "access the user interface" 
policy, the view/modify drop-down is available.

If you switch to another policy like "query provenance" which correctly doesn't 
have the view/modify drop-down, then if you go back to "access the user 
interface" policy the view/modify drop-down is now gone.


> Policies:  The view/modify drop-down should not be displayed for the "access 
> the user interface" policy
> -------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2272
>                 URL: https://issues.apache.org/jira/browse/NIFI-2272
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.0.0
>            Reporter: Andrew Lim
>              Labels: UI
>         Attachments: NIFI-2272_viewModify.png
>
>
> I reloaded my NiFi instance and selected "Policies" from the control 
> drop-down menu.  As shown in the attached screenshot, for the "access the 
> user interface" policy, the view/modify drop-down is available.
> If you switch to another policy like "query provenance" which correctly 
> doesn't have the view/modify drop-down, then if you go back to "access the 
> user interface" policy the view/modify drop-down is now gone.



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

Reply via email to