• 7
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently the jobs presented at secure/admin/SchedulerAdmin.jspa cannot be edited in any way - this includes the UI or even through database manipulation.

      We are not able to change their runtime, interval, cron expression or any parameter which they may have. Some jobs are not used and it would be great to disable them be it permanently or for troubleshooting purposes.

      The idea on this suggestion is to enhance the secure/admin/SchedulerAdmin.jspa to allow editing.

      Confluence seems to run in the same framework and it does have this feature documented on this page:

      https://confluence.atlassian.com/doc/scheduled-jobs-96567525.html

      PS: Some jobs can be disabled through feature flags if you reached this page in hopes of disabling a job.

            [JRASERVER-72546] Allow editing of Jira Scheduled Jobs

            Tony Chu added a comment - - edited

            Please implement a way to remove / delete unwanted scheduler jobs. We installed and tested a plug-in and later decided not to use it and uninstalled it. But it left behind several scheduler jobs which constantly report errors about "service proxy has been destroyed" which seems like these scheduler jobs were installed by the plugin and they are now calling that plug-in which no longer exists. The scheduler jobs page just don't provide a way to delete those jobs showing the errors which we are very certain they belong to that plug-in.

            We filed a support ticket to Atlassian, asking if we can simply delete the related DB records in "clusteredjob" table, but Atlassian support strongly discourages us to do that.

            There's also no REST API available for such purpose.

            It would be nice to have a way in that page to let us deleted the "bad boys", instead of just showing those dreadful red error numbers and we can't do anything about it.

            Tony Chu added a comment - - edited Please implement a way to remove / delete unwanted scheduler jobs. We installed and tested a plug-in and later decided not to use it and uninstalled it. But it left behind several scheduler jobs which constantly report errors about "service proxy has been destroyed" which seems like these scheduler jobs were installed by the plugin and they are now calling that plug-in which no longer exists. The scheduler jobs page just don't provide a way to delete those jobs showing the errors which we are very certain they belong to that plug-in. We filed a support ticket to Atlassian, asking if we can simply delete the related DB records in "clusteredjob" table, but Atlassian support strongly discourages us to do that. There's also no REST API available for such purpose. It would be nice to have a way in that page to let us deleted the "bad boys", instead of just showing those dreadful red error numbers and we can't do anything about it.

            The scheduler is not editable - despite this Atlassian states there is a way to update from the backend, but when asking Atlassian about the information in the documentation they say this is not available. I also inquired with Atlassian regarding scheduling Jobs that are erroneous, atlassian's reply was to delete them , no way to understand the error and the fact that they are erroneous

            .
            Would be nice to understand, to have documentation, the scheduler is not explained -there no way to edit the cron statement/frequency/the scheduler

            eleanor m kerman added a comment - The scheduler is not editable - despite this Atlassian states there is a way to update from the backend, but when asking Atlassian about the information in the documentation they say this is not available. I also inquired with Atlassian regarding scheduling Jobs that are erroneous, atlassian's reply was to delete them , no way to understand the error and the fact that they are erroneous . Would be nice to understand, to have documentation, the scheduler is not explained -there no way to edit the cron statement/frequency/the scheduler

            It would be great if you could realise native way to stop running job. 

            In the case of performance issues with slow running job there is no another way to stop it except full stopping of Jira cluster.

            Serious performance degradation using SprintManager Java API

            How to stop running job without Jira DC cluster full restart?

             

            Alexander Medchenko added a comment - It would be great if you could realise native way to stop running job.  In the case of performance issues with slow running job there is no another way to stop it except full stopping of Jira cluster. Serious performance degradation using SprintManager Java API How to stop running job without Jira DC cluster full restart?  

            Matt Doar added a comment -

            It could also be useful to expose the metrics via a REST resource to allow for better monitoring

            Matt Doar added a comment - It could also be useful to expose the metrics via a REST resource to allow for better monitoring

              Unassigned Unassigned
              a3c7c2a06f95 Filipi Lima
              Votes:
              36 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: