-
Bug
-
Resolution: Fixed
-
Low
-
3.0.5
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary:
There will be multiple WARN stack traces in the logs in regards of JIRA Service Desk Automation.
Steps to Reproduce.
- Create two Service Desk Project, e.g. SD A and SD B.
- On "SD B" navigate to the Project Administration > Automation.
- Create a "Reopen on Customer Comment" rule and confirm.
- Run the following Query:
select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID");
- There will be a result for each project Automation Rule.
- Navigate to "SD B" project administration and delete the project.
- Create a Request in "SD A" and Resolved the ticket.
- As the Reporter, access the ticket in "Customer Portal" view and comment on the ticket.
Expected Result:
- Nothing happen as there is no "Reopen on Customer Comment" rule in "SD A" without any stack trace in the logs.
Actual Result:
- Nothing happen as well but there will be a WARN stack trace like below written in the logs.
2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project'
Notes:
- Run the same query below and there will be an automation rule that did not have any project specified as it is deleted:
select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID");
- If we delete an existing Automation Rule while the Project is still exist, the row about that automation rule will still be exist.
- Tried to do the same for an Automation Rule that is deleted while the Project is still exist could not replicate the same stack trace to be thrown.
- This is WARN stack trace, it should not affect JIRA operations as it is a WARNING.
- has a regression in
-
JSDSERVER-6341 This is a regression bug of JSDSERVER-3232
-
- Closed
-
- relates to
-
JSDCLOUD-3232 Automation throws 'error.retrieving.project' WARN stack traces in the logs.
-
- Closed
-
-
JSDSERVER-3131 Warning messages on automation rule events in the log file
-
- Closed
-
-
JSMDC-3966 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
- was cloned as
-
DESK-4594 Loading...
Form Name |
---|
In my case it appears to be because there is an existing ticket with the same subject in a non-Service Desk project. We have projects with mail handlers enabled. A user sends to one of those email addresses which creates a ticket in that project. They then reply to an email on that same thread but change the destination email to the one associated with our Service Desk. Service Desk ticket is not created and the error listed is generated in atlassian-servicedesk.log.