[ 
https://issues.apache.org/jira/browse/NIFI-15409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048531#comment-18048531
 ] 

Pierre Villard commented on NIFI-15409:
---------------------------------------

This already exists: [https://nifi.apache.org/nifi-docs/user-guide.html#search] 

> Add ability to scope search to specific Process Group instead of entire NiFi 
> instance
> -------------------------------------------------------------------------------------
>
>                 Key: NIFI-15409
>                 URL: https://issues.apache.org/jira/browse/NIFI-15409
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>            Reporter: Naman Shukla
>            Assignee: Naman Shukla
>            Priority: Minor
>
> *Current Behavior:* The search feature located in the upper right corner of 
> the NiFi UI currently searches across the entire NiFi instance, returning 
> results from all process groups and nested levels.
> *Requested Enhancement:* Add the ability to limit the scope of a search to a 
> specific process group and its descendants, rather than always searching the 
> entire NiFi instance.
> *Use Case:* In large NiFi deployments with many process groups and hundreds 
> or thousands of processors, users often need to find components within a 
> specific section of their flow. Being able to search within just the current 
> process group (and optionally its child groups) would:
>  * Reduce noise in search results
>  * Improve search performance for large instances
>  * Help users navigate complex flows more efficiently
>  * Make it easier to work on specific subsections of a dataflow
> *Proposed Implementation:* Add a search scope option that allows users to 
> choose between:
>  # "Entire Instance" (current default behavior)
>  # "Current Process Group" (search only within the currently open process 
> group)
> This could be implemented as a dropdown or filter option near the existing 
> search box.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to