You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2024/10/31 12:54:00 UTC

[jira] [Created] (NIFI-13953) Improve Go To for Rule Violations

Pierre Villard created NIFI-13953:
-------------------------------------

             Summary: Improve Go To for Rule Violations
                 Key: NIFI-13953
                 URL: https://issues.apache.org/jira/browse/NIFI-13953
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Pierre Villard
         Attachments: Screenshot 2024-10-31 at 13.49.34.png, Screenshot 2024-10-31 at 13.49.50.png

When violations are reported and the associated component is not a processor there is no Go To option. In the below examples, the violation is for a connection, and there is no Go To option. It would be useful to have the Go To option for any component.
{code:java}
        {
            "enforcementPolicy": "ENFORCE",
            "scope": "e26effa4-0192-1000-7826-18bfabd139ac",
            "subjectId": "e270eaa4-0192-1000-0622-8f9af5319328",
            "subjectDisplayName": "Funnel > ",
            "groupId": "e26effa4-0192-1000-7826-18bfabd139ac",
            "ruleId": "e23b4273-0192-1000-a903-f0bcfdcdc86f",
            "issueId": "xxx",
            "violationMessage": "xxx",
            "subjectComponentType": "CONNECTION",
            "subjectPermissionDto": {
                "canRead": true,
                "canWrite": true
            },
            "enabled": false
        }{code}



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