Joseph Witt commented on NIFI-2473:

Had a nice discussion with Matt Gilman to better understand the scenario at 
play here.  The deal is that in older NiFi versions there was a bug in 
standalone mode which meant it wasn't checking the case where multiple 
components were selected and then blocking deletes which didn't account for all 
items in a chain.  This has been fixed so it appears to be a regression but 
really it was simply made more consistent.

The idea is that single selection actions like (delete, move, copy) do 
generally infer the other impacted relationships (except connection moves which 
are always explicit).  In the case of multiple component selection all items 
involved in the action (delete, move, copy) must be explicitly selected.

Let's leave this ticket open because we could either make the single select 
case and the multi-select case behave the same way single select does now or 
the way multi-select does.  I think that JoeP's expectation of behavior is the 
most intuitive.  And, as time/interest dictates we can improve this but let's 
not have the ticket lurking on any fix version until there is traction.

> UX regarding deleting components and connections regressed unintentionally
> --------------------------------------------------------------------------
>                 Key: NIFI-2473
>                 URL: https://issues.apache.org/jira/browse/NIFI-2473
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Joseph Percivall
>            Assignee: Scott Aslan
> Currently in master each of these fail but succeed in 0.x (connection is 
> coming from the source and is connected to the destination):
> destination and connection selected, attempt to delete
> source and connection selected, attempt to delete
> source and destination selected, attempt to delete
> I believe this is due to the connection being "connected" to a component 
> outside of the snippet and in the third case, the components being 
> "connected" to the connection (which is outside the snippet).

This message was sent by Atlassian JIRA

Reply via email to