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

Matt Gilman resolved NIFI-6253.
-------------------------------
    Resolution: Fixed

> UI - Process Group ID display in "Operate" palette can get out of sync when 
> process groups are removed from different sessions.
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6253
>                 URL: https://issues.apache.org/jira/browse/NIFI-6253
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.9.2
>            Reporter: Robert Fellows
>            Assignee: Robert Fellows
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> To reproduce this issue:
> # Open Nifi in 2 different browser tabs
> # Add two process groups to the canvas in one tab, then refresh the other tab 
> to get the updates.
> # Take note of the Process Group IDs displayed in the "Operate" palette when 
> selecting each one in the canvas.
> # Take note of the Process Group ID for the entire Flow  displayed in the 
> "Operate" palette (clicking on a blank spot on the canvas will update the 
> palette)
> # In one of the browser tabs, delete one of the process groups.
> # Quickly switch to the other browser tab and double click on the process 
> group you deleted in the other tab to attempt to enter that process group.
> # You should see a dialog indicating something to the effect of this process 
> group is not able to be located (this is expected)
> # Now click on a blank spot on the canvas. Notice that the process group id 
> displayed for the Flow is id for the process group that was deleted and NOT 
> for the flow.
> # Expected: Clicking on the canvas should update the process group id in the 
> "Operate" palette to the proper id following the failure to enter a process 
> group.



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

Reply via email to