[
https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302579#comment-16302579
]
Yuri commented on NIFI-4538:
----------------------------
The parent and top level PGs' names (or IDs) could be relatively long. It seems
they wouldn't fit on query match header line together with the component's
name. This design also doesn't look really clean - !Screenshot from 2017-12-23
21-08-45.png|thumbnail!.
Moving both PGs below the query match header line seems to be confusing a bit -
!Screenshot from 2017-12-23 21-42-24.png|thumbnail!. Maybe to embolden some
parts would help.
Does anybody have any ideas on this?
> 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
> 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
(v6.4.14#64029)
