[
https://issues.apache.org/jira/browse/NIFI-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184072#comment-17184072
]
Mark Payne commented on NIFI-3785:
----------------------------------
I think one of the challenges here is the fact that the Controller Services are
divorced from the canvas. It means that. "Move to Parent" would be easy to
provide. But a "Move to Child" is harder, because you then have to provide a
list of Process Groups that the service can be moved to (this involves listing
these in the UI, including Process Group ID, Name, and ideally comments. And
ensuring that appropriate permissions are checked, etc.)
Even with a Move capability, there will be a desire to cut/paste because if you
refactor your flow, you may want to move a Controller Service to a sibling
Process Group. Or down 4 levels, for example. So personally, if tackling this
now, I'd go for a Cut/Copy and Paste approach.
The stretch goal, for me, if we have the people able to work on this who have
the design/UI/UX chops, would be to change the layout of the Controller Service
table all together. Instead of a single table, it would provide something where
the parent/ancestor Process Groups and child/descendant Process Groups are
shown, along with their Controller Services, and they would be collapsible.
Currently, the table shows the Controller Service for the current group and all
ancestors. I would want to instead show each Process Group that is an
ancestor/descendant as like a stack of Process Groups that are collapsible,
each with its Controller Services. Then allow the user to drag and drop a
Controller Service from one Process Group to another.
But I'd be really happy with a cut/copy and paste (or a Move to parent/child)
for now :-D
> Allow user to move Controller Service
> -------------------------------------
>
> Key: NIFI-3785
> URL: https://issues.apache.org/jira/browse/NIFI-3785
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Mark Payne
> Priority: Major
>
> Currently, there is no way to move a Controller Service from one Process
> Group to another. I would like to be able to move a Controller Service from
> its Process Group to the "parent" Process Group in order to broaden its scope.
> The ability to move the Controller Service to a child group in order to
> narrow its scope would be convenient as well but may be difficult to provide
> an intuitive user experience around.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
