Skip to main content

Start an epic on a schedule

Some large jobs come back on a rhythm: a monthly dependency upgrade, a quarterly clean-up of old code. Instead of starting the same epic by hand each time, an automation on a schedule can file it for you. Each run files one epic per project you pick, and the epic runs its stages like one you started yourself. How epics run is in How epics and features work; how automations work is in How automations work.

Who can do this: Owners and Admins of your organization. A project's Maintainer can too, from the project's Schedules tab, for schedules that target only projects they maintain.

  1. In the sidebar, select Audit, then the Automations tab, and select New automation.
  2. On When, pick Schedule, select Edit on the Schedule line and set when it runs, such as the first Monday of each month. Read the Schedule line to check the next run, then select Next.
  3. On What, leave Action at Task. Under Target, pick Projects, then choose the projects in Run in projects. Each one gets its own epic on every run.
  4. Write the epic's brief in the description, as you would when you start an epic: the outcome you want, not the steps.
  5. In the size list, pick Epic. Then pick the involvement: Unattended lets every stage decide for itself, Guided asks before the requirements and the design are settled. An epic offers no Interactive. Pick a Priority if it matters, then select Next.
  6. On Name, enter a name you will recognize in the list, such as Monthly dependency upgrade, and select Create. The automation's page opens.
  7. Open its Settings tab. Under Action, set Throttle to cap how many subtasks run at once, or to Manual so each subtask waits for you to start it. Pick who it is Assigned to: a guided epic's questions go to that person. Select Save.

To try it without waiting for the schedule, select Run now on the automation's page; the run's line says how many epics it filed.

What to expect​

  • An epic an automation starts is hidden, off the default task board. Turn on the board's Hidden filter to see it, as in Hide an epic and its subtasks from the board. Choose Leave as draft under Start instead to have each epic wait on the board for you to start it.
  • A run files nothing for a project whose epic from an earlier run is still open, so a slow epic never piles up a second one. See What a run skips.
  • Epics an automation files tell no one when they finish. Check the result as in Check what a finished epic delivered.