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

ASF subversion and git services commented on NIFI-11389:
--------------------------------------------------------

Commit 45713f6eec82e0a4bcc2aabd965bbf3f5c541c46 in nifi's branch 
refs/heads/support/nifi-1.x from NissimShiman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=45713f6eec ]

NIFI-11389 Fixed controller services's link to referencing controller (#8194)

services of lesser scope

This closes #8194 

> Controller Services's link to referencing Controller Services components not 
> always working
> -------------------------------------------------------------------------------------------
>
>                 Key: NIFI-11389
>                 URL: https://issues.apache.org/jira/browse/NIFI-11389
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M1, 1.20.0, 1.19.1
>            Reporter: Nissim Shiman
>            Assignee: Nissim Shiman
>            Priority: Major
>              Labels: backport-needed
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Controller Services' Setting tab has a _Referencing Components_ section on 
> the right side.
> There are hyperlinks to the Processors and/or Controller Services which 
> reference this controller service.  These links do not always work when 
> referencing controller services.
> To reproduce:
> Create StandardRestrictedSSLContextService on top level nifi graph (i.e. 
> right click top level grid -> Configure -> Controller Services)
> Create Process Group
> Inside Process Group create DistributedMapCacheServer
> and point _SSL Context Service_ to StandardRestrictedSSLContextService just 
> created
> Go to StandardRestrictedSSLContextService's Setting's tab and verify 
> DistributedMapCacheServer appears in the _Referencing Components_ section.
> Clicking on the link to DistributedMapCacheServer will not take us to that 
> controller service.



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

Reply via email to