Large stack trace thrown when unable to process issue by mail
Description
Hi team, I noticed that our logs had been blowing up recently and one of the stack traces that was responsible seems to be coming from your plugin (uploaded an example as example_stack).
What is happening here is a mail handler configured as comment only, and when an email comes in to that inbox that does not have a Jira issue key in the subject it throws that error. I have mitigated this on our side using inbound routing rules in the affected inbox, but wanted to bring it to your attention.
Let me know if there is any other info I can provide!
Environment
Activity
Hey Deniz, doesn't look like I got a stack trace for that, any packages I could enable debug logging on to get better resolution?
com.deniz.jira.reminders is the package of the add-on. But exceptions are always logged.
Not seeing anything from that package in the logs, so not totally sure what's up. I've noticed that if I give it some time I don't get the error, so I am slowly adding them back over the course of the day. Might be something funky with Data Center cache replication? Who knows ¯_(ツ)_/¯
While I have you - is there any way of determining which projects are using the plugin?
If you can run SQL agains the Jira database you can inspect AO_AFAA51_REMINDER table. If your reminders are set to auto delete, it will not contain already sent reminders but it will show all of active reminders. ISSUE_ID column shows related issue. Using "jiraissue" table you can find which project it is.
