User Guide for Enterprise Sprint Automation: Installation, Configuration, and Bulk Creation in Jira Cloud

How to automate sprints in Jira: this guide shows you how to install, configure, and operate Enterprise Sprint Automation on Jira Cloud — automatically starting and closing sprints, rolling unfinished work into the next sprint, and bulk-creating sprints for SAFe PI and quarterly planning across every board.

Audience: Jira space administrators and Scrum Masters.

Try it free: Enterprise Sprint Automation — Bulk Create & Auto Start/End on the Atlassian Marketplace

This guide is organized so that you can read it top-to-bottom on first install, or jump to the task you need.

1. Installation

1. Sign in to Jira Cloud as a site administrator.

2. Go to Apps → Explore more apps and search for Enterprise Sprint Automation — Bulk Create & Auto Start/End for Jira.

3. Click Get it now and accept the requested permissions.

4. Wait for the install to complete. On first install the app initializes its data store — this typically completes within a minute.

The app is ready to use as soon as the install finishes.

2. Permissions required

The app requests only the Jira scopes it needs:

No other scopes are requested.

3. Configuring a board

Open the Jira space that contains the Scrum board you want to automate and navigate to Space settings → Enterprise Sprint Automation Configuration.

For each Scrum board you see a row with the following settings:

Click Save. Changes take effect on the next scheduled check (within 5 minutes) and on the next sprint event from Jira.

4. Working-days calendar

From the same configuration page, open the Working days panel for the board and tick the days the team actually works. The app will skip non-working days when calculating sprint start and end times.

5. Bulk sprint creation (PI planning, quarterly planning, and more)

Space admins see a Bulk Sprint Creation item in the space sidebar. This page is built for enterprise planning ceremonies — SAFe Program Increment (PI) planning, quarterly planning, half-year rollouts and any other event where you need to provision an entire team's (or an entire Agile Release Train's) future sprints in one sitting.

Typical scenarios

The two creation flows

1. Interactive form — choose one or more boards, a starting sprint name, a duration (1, 2, 3 or 4 weeks), and the number of sprints. The page previews every sprint name and every start/end date. Click Create to submit.

2. CSV import — download the template, fill in names and dates, and upload. This is ideal when your PMO distributes the PI / quarterly schedule as a spreadsheet and you want Jira to match it exactly.

Multi-board mode

Multi-board mode applies the same cadence to several boards at once, so every team in a PI or program lands on the same rhythm. Combine it with a shared naming template (for example ART1 PI3 Sprint {{n}}) to keep sprint names consistent across the whole ART.

For a worked example of using bulk creation for SAFe PI and quarterly planning, see SAFe for Realists: Streamlining Quarterly Planning with Bulk Sprint Creation on the Divim blog.

Working-days calendar

The per-board working-days calendar (see section 4) is honored by Bulk Sprint Creation as well, so sprint start and end times automatically skip weekends, company-wide holidays, IP weeks, and regional non-working days.

Parallel sprints

Enable parallel sprints on a board when that team plans and runs several workstreams concurrently during a PI. Multiple future sprints will be created and kept in sync.

Large batches

If you request a large number of sprints at once — which is typical during PI planning — the app processes them in the background. You will see progress in the Application logs on the admin configuration page, including any automatic rate-limit back-offs.

Bulk deletion

You can also bulk-delete future sprints that were created in error or that need to be regenerated after a PI-plan change. Active and closed sprints cannot be deleted through the UI — this is a deliberate safeguard so that in-flight and historical work is never lost.

6. Application logs

The admin configuration page exposes a Logs tab that shows the last 500 log entries emitted by the app. Each entry has an ISO timestamp and a short message. Use this tab first when investigating any unexpected behavior.

7. Sprint Report Cards

Every time the app starts or closes a sprint, it generates a Sprint Report Card automatically. Report cards are available in two places:

• Admin configuration page → Report Cards tab — a global view covering every board managed by the app, shown in reverse chronological order.

• Project sidebar → Bulk Sprint Creation → Report Cards — a per-board view filtered to the board whose project page you are viewing.

Each card shows:

Click Copy report on any card to copy a plain-text summary to the clipboard. This is useful for posting a sprint review to Confluence, Slack, or email without leaving Jira.

Report cards are stored automatically and capped at 500 entries; older cards are pruned as new ones arrive.

8. Board Options panel

For Jira administrators who prefer to manage automation settings from within a board view rather than the global admin page, a Board Options page is available in the project sidebar (under the same Bulk Sprint Creation entry).

The Board Options page shows the automation settings for that specific board and lets a Jira administrator save changes in-context. The same settings are also configurable from the global admin configuration page; whichever was saved last takes effect.

If the board has not yet been added to automation, the page shows a message directing the user to the global admin configuration page.

9. How the scheduled check works

Every five minutes, the app checks all opted-in boards and:

1. Reads the current sprint state for each board.

2. Closes any active sprint whose end date has passed, moves unfinished work according to your configuration, and starts the next sprint.

3. Jira sprint events (start, close, update, etc.) are also observed in real time — the app coordinates these with its scheduled checks so each sprint action is performed exactly once.

10. Troubleshooting

11. Uninstalling

Removing the app from the Apps → Manage apps page stops all automation immediately. Atlassian deletes the app's Forge SQL and Forge KVS data as part of the standard Forge app-removal lifecycle. See the Privacy Policy for details.

12. Getting help

• Support email: support@divim.io

• Trust Center: https://public.docs.divim.com/wiki/spaces/DC/pages/3192520706

• Get the app: Enterprise Sprint Automation on the Atlassian Marketplace

When contacting support, please include:

• your Atlassian site URL,

• the board ID or sprint ID involved,

• a copy of the relevant lines from the Logs tab,

• and the approximate time (with timezone) at which the problem occurred.

Further reading on divim.io

Learn more about automating the Jira sprint lifecycle at scale:

• SAFe for Realists: Streamlining Quarterly Planning with Bulk Sprint Creation — using Bulk Sprint Creation for SAFe PI and quarterly planning.

• Automating the Chaos: A Guide to Stress-Free Sprint Closures at Scale — auto-closing sprints across many boards.

• The Future of Agile Governance: Standardizing Sprints Across Enterprise Boards — multi-board standardization and governance.

• More on the Divim blog and the Atlassian Marketplace listing.