Docs → Encore
Encore docs
Encore creates Jira issues on a schedule: daily, weekly, every N weeks, monthly, on business days or by cron. Project admins manage schedules under Project settings → Encore, and anyone with Create Issues can start one from an issue with Make recurring.
Getting started
Before you install
- Jira Cloud. Encore is a Forge app (Runs on Atlassian).
- Project admin permission to open Project settings → Encore and manage every schedule in that project.
- The Create Issues permission to use Make recurring on an issue (a project admin can switch this off).
- A Jira Software board in the project if you want new issues added to a sprint.
- Jira admin access to open the cross-project view Encore — all schedules (Standard plan).
Install and first use
- Open Encore in your projectGo to Project settings and choose Encore in the sidebar. The page shows Encore schedules with four views: Schedules, Templates, Holidays and Settings.
- Create a scheduleClick New schedule. Give it a Name, then under What each run does pick Create an issue, Use template, Reopen an existing issue or Clone an existing issue. For a new issue, choose the Issue type and write the Summary and Description.
- Set the timingPick a Cadence (Daily, Weekly, Every N weeks, Monthly, Monthly — business day, Every business day, or Advanced (cron)), then the Time of day (HH:MM, 24h) and Timezone. The timezone defaults to your browser's. Check the Upcoming runs list in the editor before saving.
- Save and checkClick Save schedule. Each schedule row shows its next run and last outcome. Use Run now to create one issue immediately without changing the schedule, and open the history to see every run.
- Or start from an issueOn an issue, open the ••• menu and choose Make recurring. Under Each time it runs, choose Create a new copy or Reopen that issue, set the timing and save. Issues created this way are reported by you.
- Ask RovoIf your site has Rovo, open the Encore Recurring Issues agent or ask Rovo chat What recurring issues will be created this week? It lists your schedules and upcoming runs, creates a daily, weekly, every-N-weeks, monthly or business-day schedule, and pauses or resumes one. Rovo shows the details and asks you to confirm before it creates or changes anything. It uses the same permissions and free-plan limit as the app.
Configuration
Cadences
- Daily and Weekly (pick the Days of week).
- Every N weeks (biweekly, sprints): set Repeat every (weeks) and a Starting (YYYY-MM-DD) date.
- Monthly: a Day of month, the last day, or By weekday (e.g. 2nd Tuesday, last Friday).
- Monthly — business day: the first or last business day of the month.
- Every business day: Monday to Friday, minus the project's holidays.
- Advanced (cron): a standard 5-field expression (minute hour day-of-month month day-of-week), e.g.
0 9 * * 1-5. Cron schedules fire at most once per hour.
Timezones
Every schedule keeps its own timezone, and daylight-saving changes are handled. Times are entered as 24-hour HH:MM.
Weekends and holidays
Each project has its own holiday list on the Holidays view: add dates one at a time (YYYY-MM-DD) or paste a list, one per line or comma-separated. Business-day cadences skip these dates.
Monthly (by day of month) and every-N-weeks schedules can choose what happens when a run lands on a weekend or holiday: Don't adjust, skip that run (Skip that month), Move to the previous business day or Move to the next business day.
Date tokens
Put tokens in the summary or description and each issue is named for its own run date, in the schedule's timezone. Example: Payroll {{monthYear}} becomes Payroll November 2026.
Tokens: {{date}}, {{day}}, {{weekday}}, {{month}}, {{monthShort}}, {{monthNumber}}, {{monthYear}}, {{year}}, {{quarter}}, {{week}} (ISO week). Add an offset in the token's own unit, e.g. {{monthYear-1}} for last month. Unknown tokens are left as typed.
Create, template, clone or reopen
- Create an issue: a new issue each run, with optional pre-filled Assignee, Priority, Labels, Components, Reporter and custom fields.
- Use template: create from a template on the Templates view. Recurring a multi-level template (epic → story → sub-task) needs the Standard plan; you can still author, import and save one disabled on Free. Templates exported from Prefab can be pasted in and imported.
- Clone an existing issue: copies the Issue to clone as it is at run time and links the copy to it (default Link type:
Cloners). Copy its sub-tasks too (Standard plan) copies up to 50 sub-tasks. - Reopen an existing issue: moves the Issue to reopen back to a To Do status each cycle. If it is still open, that run is skipped and logged.
- Skip creating a new issue if the previous one is still open: optional for new-issue schedules.
After each issue is created
- Add to a sprint on board: Active sprint, Next (future) sprint, or Active sprint, or the next one between sprints.
- Move it to status: a status you pick.
- Set a due date: a number of calendar days or business days after the run.
- Link it to the issue the previous run created.
- If one of these steps fails, the issue still exists and the run history records why.
End conditions
Under Ends, choose Never, After a number of runs or On a date.
Who can schedule
On the Settings view, the toggle Let anyone who can create issues make issues recurring is on by default. When on, people with Create Issues can use Make recurring and manage the schedules they created; only admins can use templates or edit other people's schedules. When off, only project admins can create or change schedules.
Cross-project view
Jira admins can open Jira settings → Apps → Encore — all schedules to see every schedule across projects with its health (Healthy, Needs attention, Disabled). It is read-only and links back to each project's Encore page. This view is part of the Standard plan.
Language
Available in English, German, French and Spanish. The app follows each person's Jira language setting; Rovo answers, exports and comments the app posts stay in English.
Free vs Standard
Plans and prices below are read from the same pricing file the app uses. Atlassian bills per user per month on your site's user tier, and the price per user steps down at larger tiers. See all pricing.
Free
Free
- Up to 5 active schedules, at any site size
- Daily, weekly, every N weeks (biweekly, sprints), monthly, last-day & nth-weekday, business days, and cron
- Weekend & holiday handling — skip, or move to the previous/next business day
- Date tokens in summary & description — {{date}}, {{monthYear}}, {{quarter}} …
- Create a new issue each run, or reopen the same issue
- Anyone with Create Issues can make their own issues recurring (admin can turn off)
- After each issue: add to the active or next sprint, move to a status, set a due date (+N business days), link to the previous issue
- Runs within ~5 minutes of the scheduled time; Run now, Duplicate, 14-day upcoming agenda
- Any timezone (DST-correct), missed-run catch-up, upcoming-runs preview
- End conditions — stop after N runs or on a date
- Field pre-fill — assignee, priority, labels, components, custom fields
Standard
$0.50 / user / month
Free for sites up to 10 users. 30-day free trial.
- Everything in Free
- Unlimited active schedules
- Multi-level hierarchy templates (epic → story → sub-task)
- Import templates from Prefab (portable)
- Admin view of every schedule across all projects
Limits
- Free plan: up to 5 active (enabled) schedules across the whole site, not per project. Disabled schedules don't count. Standard removes the cap.
- Recurring a multi-level template and copying sub-tasks when cloning need the Standard plan, as does the cross-project view.
- If a paid licence lapses, only the 5 oldest enabled schedules keep running and hierarchy-template schedules are skipped.
- The scheduler checks every 5 minutes, so issues land within about 5 minutes of the scheduled time.
- Cron schedules fire at most once per hour.
- Missed-run catch-up looks back 48 hours and creates up to 10 missed issues per schedule per run.
- Run history keeps the latest 50 entries per schedule.
- Clone mode copies at most 50 sub-tasks.
- The cross-project view lists up to 250 schedules; open a project's Encore page for the rest.
Data & privacy
What Encore stores
- Everything is kept in Forge hosted storage for your install, inside your Atlassian tenant. The manifest declares no external endpoints, so nothing is sent to Datum servers.
- Schedules: name, project, what each run does, issue fields and pre-fill values, cadence, time of day, timezone, post-create actions, end condition, and the last created issue key.
- Two Atlassian account IDs per schedule: the person who created it and the configured reporter.
- Run history per schedule: time, outcome (created, reopened, skipped or failed), created issue key and reason, capped at 50 entries.
- Per-project holiday dates, issue templates, and the project's on/off setting for who may schedule.
- Encore reports stored account IDs to Atlassian's personal data reporting each week and erases an account's ID from schedules when Atlassian reports the account closed.
Encore runs on Atlassian Forge. Data it stores sits in Forge hosted storage for your site, which Atlassian pins to your product's region. See Trust & security, the Privacy Policy and the DPA.
Permissions (scopes)
| Scope | Why Encore needs it |
|---|---|
read:jira-work | Read projects, issue types, fields and issues (for cloning, reopening and checking whether the previous issue is open). |
write:jira-work | Create issues, transition them, set due dates, and link or reopen them. |
storage:app | Store schedules, templates, holidays, settings and run history in Forge hosted storage. |
report:personal-data | Report the stored account IDs to Atlassian's personal data reporting API. |
read:sprint:jira-software | List a board's sprints to find the active or next one. |
write:sprint:jira-software | Add a newly created issue to a sprint. |
read:board-scope:jira-software | List the project's boards in the schedule editor. |
read:project:jira | Read project details used when listing boards and sprints. |
FAQ & troubleshooting
An issue wasn't created on time. What happened?
Issues land within about 5 minutes of the scheduled time. Check the schedule's run history: each run is logged as created, reopened, skipped or failed, with a reason. A banner at the top of the Encore page lists schedules whose last run failed. Also check that the schedule is enabled, that the date isn't a holiday or weekend your adjustment rule skips, and that the schedule hasn't hit its end condition.
Forge missed a run. Will Encore catch up?
Yes, for single-issue schedules that have run before and don't use Skip creating a new issue if the previous one is still open. Encore looks back 48 hours and creates up to 10 missed issues per schedule. Date tokens use each missed run's own date. Template schedules create only the current run.
Can a run create the same issue twice?
Encore claims each run before it acts, so a failure becomes a missed run rather than a duplicate.
Why was a run skipped?
In reopen mode, or with Skip creating a new issue if the previous one is still open, a run is skipped while the previous issue is still open. Skipped runs are recorded in the history.
I see "Upgrade for unlimited schedules" when saving.
The free plan allows 5 active schedules across the whole site. Disable another schedule or upgrade to Standard. Editing a schedule that is already enabled is never blocked.
Make recurring says "Ask a project admin".
A project admin has turned off Let anyone who can create issues make issues recurring in Project settings → Encore → Settings, or you don't have Create Issues in that project.
Reopen mode didn't move my issue back to To Do.
Encore needs a workflow transition from the issue's current status into a To Do status. If the workflow has none, the run fails and the history shows why.
Does Run now change the schedule?
No. Run now acts on the schedule once, immediately; its regular timing is unchanged.
Changelog
Every release and what changed: Encore changelog.
Getting help
Email support@datadir.co with your site URL and what you saw. Our target is a first response within 1 business day. See Support for what to include, and Status for known issues.