You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cant name exact steps to reproduce the issue, but we have plugin failures from time to time with following error in the logs:
"msg":"Plugin failed to ServeHTTP, RPC call failed","plugin_id":"jira","error":"connection is shut down"}
"msg":"Plugin failed to ServeHTTP, muxBroker couldn't accept connection","plugin_id":"jira","serve_http_stream_id":2922,"error":"timeout waiting for accept"}
"msg":"Health check failed for plugin","id":"jira","error":"Plugin RPC connection is not responding"}
"msg":"error closing client during Kill","plugin_id":"jira","wrapped_extras":"errconnection is shut down"}
"msg":"RPC call OnDeactivate to plugin failed.","plugin_id":"jira","error":"connection is shut down"}
"msg":"plugin failed to exit gracefully","plugin_id":"jira"}
"msg":"Access to route for non-existent plugin"
On log level turned to debug we observed following error message over and over again:
It seems that error appears when someone do some operation with ticket that have no priority field set.
The text was updated successfully, but these errors were encountered:
DummyThatMatters
changed the title
Plugin cruches from time to time on getIssueFieldValue method on issues with no priority set
Plugin crushes from time to time on getIssueFieldValue method on issues with no priority set
Nov 16, 2021
DummyThatMatters
changed the title
Plugin crushes from time to time on getIssueFieldValue method on issues with no priority set
Plugin crashes from time to time on getIssue FieldValue method on issues with no priority set
Nov 16, 2021
I cant name exact steps to reproduce the issue, but we have plugin failures from time to time with following error in the logs:
On log level turned to debug we observed following error message over and over again:
It seems that error appears when someone do some operation with ticket that have no priority field set.
The text was updated successfully, but these errors were encountered: