[jira] [Updated] (NIFI-4997) Actions taken on process groups do not appear in flow configuration history
[ https://issues.apache.org/jira/browse/NIFI-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-4997: -- Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: Patch Available) > Actions taken on process groups do not appear in flow configuration history > --- > > Key: NIFI-4997 > URL: https://issues.apache.org/jira/browse/NIFI-4997 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.4.0 > Environment: CentOS 7, Docker >Reporter: Craig Becker >Assignee: Matt Gilman >Priority: Major > Fix For: 1.7.0 > > > Selecting a process group and executing a stop or start action does not cause > anything to be logged in the flow configuration history. The current behavior > makes it impossible to trace who/when a process group was turned off. > > The expected/desired behavior would be to either add a log entry per > processor that was stopped/started, or to log that the process group was > stopped/started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-4997) Actions taken on process groups do not appear in flow configuration history
[ https://issues.apache.org/jira/browse/NIFI-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-4997: -- Status: Patch Available (was: In Progress) > Actions taken on process groups do not appear in flow configuration history > --- > > Key: NIFI-4997 > URL: https://issues.apache.org/jira/browse/NIFI-4997 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.4.0 > Environment: CentOS 7, Docker >Reporter: Craig Becker >Assignee: Matt Gilman >Priority: Major > > Selecting a process group and executing a stop or start action does not cause > anything to be logged in the flow configuration history. The current behavior > makes it impossible to trace who/when a process group was turned off. > > The expected/desired behavior would be to either add a log entry per > processor that was stopped/started, or to log that the process group was > stopped/started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)