-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
Having one (or many) Service Desks processing mails can cause the database to clog really fast. There is currently the option to execute the database cleaner every certain time, with the minimum being 14 days. It would be good to have the option for it to be executed more often than that or to execute it manually.
- relates to
-
JSDSERVER-4340 Mails should be removed from mailitemchunk table after being successfully processed
- Gathering Interest
[JSDSERVER-6195] Allow executing the Database cleaner more often or on demand (Global Mail Settings)
Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Link | New: This issue relates to JSDSERVER-4340 [ JSDSERVER-4340 ] |
Workflow | Original: JAC Suggestion Workflow [ 3081891 ] | New: JAC Suggestion Workflow 3 [ 3647567 ] |
Support reference count | New: 1 |
Description | Original: Having one (or many) Service Desks processing mails can cause the database to clog really fast. There is currently the option to execute the database cleaner every certain time, with the minimum being 14 days. It would be good to have the option for it to be executed more often than that, allowing Administrators to set it to a week, or even less than that. | New: Having one (or many) Service Desks processing mails can cause the database to clog really fast. There is currently the option to execute the database cleaner every certain time, with the minimum being 14 days. It would be good to have the option for it to be executed more often than that or to execute it manually. |
Summary | Original: Allow executing the Database cleaner more often (Global Mail Settings) | New: Allow executing the Database cleaner more often or on demand (Global Mail Settings) |
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center