Whats the difference between "The Scheduler" plugin and using automation's "scheduled" trigger

Question

I'm looking to build out some automated workflows using Jira. specifically to create daily tasks for the team each day. There are 2 options i'm considering for this:

- "The Scheduler" plugin on the Atlassian Marketplace

https://marketplace.atlassian.com/apps/37456/the-scheduler?hosting=cloud&tab=overview

- Using the Automation functionality withing Jira, specifically the "Scheduled" Trigger to kick off the automation.

Obviously, there is a cost to using "The Scheduler" plugin, so i'm just wondering if there is any benefit that the plugin has over Automation?

Thanks.

Lucas Modzelewski _Lumo_ · Answer

We use Automation for 'action' like comments on Service Desk and closing subtasks - set it forget it.

One of the advantages of The Scheduler is the ability to grant access to app. Automation focuses on Project and Global Admins, while access to The Scheduler can be granted in project settings to: user, groups or project roles - it decrease Admins overhead.

For issue creation, when details are changing we keep using The Scheduler, where everyone (with granted access) can tweak and update their tasks, when needed.
Scheduled Issue creation can be as easy as using "Schedule Issue" option, on existing Jira issue. Then all issue data is populated in the wizard (and can be updated), the only thing left is to set the trigger details - so it's very easy to start using the app on repetitive tasks.

The price is the same regardless of executions. There are no limits of usage (even for Free Jira tier).
Schedulers goal is to create Jira issues on time. If for some reason the task was not created as planned or execution was incomplete - our notification module sends emails. This allows users (eg reporter, assignee) to take direct actions to solve the problem, without even bothering Administrators.

If you have few essential tasks Automation is the way to go :)
But when you have lots of task created each month on schedule (or as template), this ability to be managed and maintained by users is making the difference - it's when The Scheduler is more user & admin friendly ;)

Cheers,

Łukasz

PS. We have some features coming up next on our Roadmap: The Scheduler for Jira Cloud

Daniel Anderson_dbcgpv · Answer

Thanks for the response Lukasz,

I notice that within Automation there is also the ability to schedule a task using a cron expression for future tasks.

Given this, i'm just wondering what benefit there is to using The Scheduler, or has it been made obsolete by the release of the in-built automation feature?

Kind Regards,

Daniel

Lucas Modzelewski _Lumo_ · Answer

Automation allows you to automate some routine tasks, it's like a shortcut for some of your daily action, with if -> then logic, which is great.

The Scheduler allows you to easily (3 step wizard) plan creation of tasks in future. On 2nd step, you set up issue details - fields from create issue screen. The last step of the wizard is place where you set "when" to create task. There are multiple trigger types making it quite flexible. Starting with simple cron builder, with place for advanced cron expressions, through interval trigger (eg. for tasks every 2 weeks, days, month), or triggers like "Run once" to create task in future when it's needed.

All Scheduled Issues can be executed when needed with "Execute" action. But there is also "Manual" trigger type, which makes app can be used as a template tool. You can even customize the status in which issue will be created: Documentation: Set initial issue status

Recently we made some updates, here you can check out the view of the table in our refreshed UI: Documentation: Scheduled Issues table overview

Cheers,

Łukasz