Skip to content
Epicycle by RETEK
For Jira Cloud

Epicycle: Epic & Work Item Templates

Save an epic as a template and run it again with variables, working-day due dates and a preview before anything is created.

Runs on Atlassian · English and Polish

What it does

Turn a finished epic into a reusable template. Each run creates the epic, its work items and subtasks in template order, counts due dates in working days from one date, fixes configuration problems in a preview and resumes without silent duplicates.

Save the epic you already have

Open an epic, choose Save as template, and its work items and subtasks become a template: summaries, descriptions, work types, priorities, labels and due dates as working days from the epic's start or end. Write {{Client}} in a summary to make it a variable.

See problems before anything is created

The preview checks the target space as you: missing work types (with a replacement of the same level), disabled subtasks, required fields the template leaves empty, your permission to create. Fill text, number, date and single-select fields once per work type, right in the preview.

Never silently, never twice

Work items are created in the background in waves, with progress and a report of what was created, skipped or failed and why. An interrupted run resumes and creates only what is missing; when the outcome is unclear, it stops and lists the work items to check instead of guessing.

Know where a template works before you roll it out

One click checks a template against every space you can create in: missing work types, disabled subtasks, required fields. Each space is ready, needs one answer in the preview, or is blocked with the reason. Nothing is created.

Getting started

Three short screen recordings, from the first template to the first run. The captions are part of the picture; the same steps are written under each video.

1. Save an epic as a template

What the video shows (about 46 seconds, no sound):

  1. Open an epic whose work items you want to reuse.
  2. Open the Actions menu (•••) and choose “Save as template”.
  3. Epicycle reads the epic, its child work items and their subtasks: 13 work items here.
  4. Due dates are saved as working days from the start of the epic, so every run moves them to its own date.
  5. Names in double braces, like {{Client}}, become variables you fill in once per run.
  6. Saved. The template is now in the library for everyone who uses Epicycle on your site.
  7. Find it under Apps → Epicycle. Next: run the template.

2. Run a template

What the video shows (about 85 seconds, no sound):

  1. Open Apps → Epicycle. The library lists every template on your site.
  2. Choose “Run” next to the template.
  3. Pick the space, the start date and a value for each variable.
  4. Before anything is created, Epicycle checks the space as you. Here the Task work type does not exist.
  5. Choose a replacement of the same level, then preview again.
  6. Nothing blocks the run now. The preview lists every work item with its due date.
  7. Work items are created in the background. You can watch the progress or close the page.
  8. Done. The report links the new epic and every work item, in the order of the template.
  9. If a run is interrupted, “Resume” creates only what is missing. When the outcome is unclear, Epicycle stops and asks you.

3. Check where a template works

What the video shows (about 42 seconds, no sound):

  1. Rolling a template out to several teams? Check the spaces first.
  2. Open the template and choose the “Where it works” tab.
  3. Epicycle checks work types, subtasks and required fields in every space where you can create work items.
  4. Each space is ready, needs one answer in the preview, or is blocked — with the reason. Nothing is created.
  5. “Run here” starts a run with the space already chosen.
  6. That is all you need to start. Templates stay on your site; export works even without a subscription.

Details

Epicycle saves an epic with its work items and subtasks (up to 60) as a template and creates the whole tree again in a company-managed space.

  • Variables: write {{Client}} or {{Start}} in summaries and descriptions; type the values once per run.
  • Due dates in working days from one date, with an optional Polish, German or US holiday calendar.
  • A preview before anything is created: missing work types, disabled subtasks, required fields and your permissions, with the fixes in the same place.
  • Apply a template under an existing epic, or create a new epic from the template library.
  • Resume an interrupted run without silent duplicates; a report for every run.
  • Export and import templates as JSON, also without an active subscription.
  • Runs on Atlassian: no servers of our own, nothing is sent to us. English and Polish.

Questions before you try it?

Write to support@retek.app.