A rollout’s page shows what the rollout wrote on each board and how each board ended. From it you retry a board that was not applied, or roll boards back to the settings they had before.

Open a rollout #

1. Open Templates and select the template’s name.
2. On its Rollouts card, select the rollout’s start time.

Follow the rollout #

The page “Rollout of Northstar team flow” shows the version and the start time. Its state is “Queued”, “Applying”, “Applied”, “Partly applied”, “Failed”, “Rolling back”, “Rolled back” or “Detached”. “Detached” means the rollout no longer governs its boards, which keep their settings.

“Paused” means no board is written, or restored during a rollback, while the pause lasts. Its starter or a Jira administrator can resume or cancel it under Administration → Imports and jobs, where its state allows.

The Boards in this rollout card counts the boards by outcome. Each row has:

• Outcome: “Waiting”, “Applied”, “Partly applied”, “Skipped”, “Conflict”, “Failed”, “Rolled back” or “Rollback conflict”.
• Detail: why the row ended so.
• Versions: “Wrote: …” with each kind’s version change, and “Restores to: …” for a rollback.
• Updated: when the row last changed.
• Actions: Retry or Roll back.

A rollout is complete only when every board is applied.

Detail says why a board ended as it did, for example:

• “This board’s settings changed after the dry run. No rollout changes were applied to this board. Run a new dry run, review the changes, and confirm again.” (“Conflict”): select Retry for a fresh dry run.
• “This board could not be written. What was written on it before the failure is not stated here, so read the board before acting on it. Open the rollout screen and run a fresh dry run over this board to see the plan that would apply now.” (“Failed”): open the board’s Configure first, then run a new dry run from the template’s Roll out page. A failed row has no Retry.
• “Only part of this rollout was written to this board. A setting on the board changed while it was being written, so nothing more was written to it.” (“Partly applied”): Versions names what was written. Select Roll back to undo it, or run a new dry run for the rest.
• “This board’s quick filters were not checked with Jira for the person who ran the rollout, so nothing was written to it. Retry this board to check them.”: select Retry.
• “Another template governs this board, and settings on it are locked, so nothing was written. Only an administrator may switch the board to this template.”: ask a Jira administrator to roll this template out to the board.
• “Independent approval is required on this board, and this version was approved by its own author, so nothing was written.”: have another approver review a version, then roll it out.

For a “Conflict” or “Skipped” board, select Retry on its row. A retry starts with a fresh dry run of that board, then Apply this board. A board skipped because it already held every setting, or because it was deleted, has no Retry.

Roll back boards #

Select Roll back on a row, or Roll back boards for several. “Roll back 2 boards of this rollout?” shows each board’s action first: “Will be restored”, “Will be detached” (the rollout wrote only policies or views), “Refused: edited since”, “Refused: locked since”, “Nothing to restore” or “Already rolled back”.

A rollback restores the flow definition, the calendar and the layout to the versions the board had before. The WIP policies and saved views stay on the board, detached from the template. A board edited since the rollout is refused (“Refused: edited since”), and so is a setting the site has locked since.

Enter a Reason, kept in the audit trail, and select Roll back 2 boards. This cannot be undone. After you confirm, What the rollback did, board by board lists each result.

For example, Dana Whitfield rolls Northstar team flow out to Platform team and Support triage. The Boards in this rollout card counts both as “Applied”, and each row’s Versions reads “Wrote: …” with the flow definition and calendar versions it wrote. If Platform team turns out wrong, Dana selects Roll back on its row, and “Will be restored” says its earlier settings come back.

If something looks off #

• “Only the person who ran this rollout, or an administrator, can retry or roll it back.”: ask that person.
• “This rollout is not complete: not every board was applied.”: read the Detail of each row that is not “Applied”, and retry the “Conflict” and “Skipped” ones.
• “This needs Board owner on this board, which you no longer hold.”: ask a Board owner of that board.
• “The template version this rollout applied can no longer be rolled out, so this board cannot be retried. Roll out a published version of the template instead.”: roll out the template’s published version (Roll out a template).