[
https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347642#comment-16347642
]
ASF GitHub Bot commented on NIFI-4538:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2364
@yuri1969 The introduction of the Parent group makes a lot of sense.
However, I thought the idea of the Top level group was a little confusing.
Technically, the Top level group is the Root group we just do not support
navigating out of it. As an alternative, I wanted to suggest maybe changing
that part to return the nearest versioned group (if applicable) that was just
released in 1.5.0. This would be helpful in identifying which versioned flow
the component exists in.
Thoughts?
> Add Process Group information to Search results
> -----------------------------------------------
>
> Key: NIFI-4538
> URL: https://issues.apache.org/jira/browse/NIFI-4538
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Matt Burgess
> Assignee: Yuri
> Priority: Major
> Attachments: Screenshot from 2017-12-23 21-08-45.png, Screenshot from
> 2017-12-23 21-42-24.png
>
>
> When querying for components in the Search bar, no Process Group (PG)
> information is displayed. When copies of PGs are made on the canvas, the
> search results can be hard to navigate, as you may jump into a different PG
> than what you're looking for.
> I propose adding (conditionally, based on user permissions) the immediate
> parent PG name and/or ID, as well as the top-level PG. In this case I mean
> top-level being the highest parent PG except root, unless the component's
> immediate parent PG is root, in which case it wouldn't need to be displayed
> (or could be displayed as the root PG, albeit a duplicate of the immediate).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
