Skip to content

Release Statuses

1 min read

Release status controls whether execution work is allowed inside a release.


The release is planned and ready to begin.

  • Executions are allowed.
  • Hawzu shows a warning before execution work proceeds.
  • The release can move to In Progress, Paused, Completed or Archived.

Use this status when a release is prepared but active testing has not fully started.


The release is actively under test.

  • Executions are allowed.
  • Execution work has no release-status warning.
  • The release can move to Paused, Completed or Archived.

Use this status during active test execution.


The release is temporarily on hold.

  • Executions are blocked.
  • The release can move back to In Progress, or to Completed or Archived.

Use this status when testing should stop temporarily.


The release work is complete.

  • New executions are blocked.
  • Execution edits are blocked.
  • The status can still be changed: reopen the release by moving it to In Progress or Paused, or move it to Archived.

Use this status after testing is finished. Only Archived locks a release’s status.


The release is preserved as a historical record.

  • Executions are blocked.
  • Modifications are blocked.
  • Status changes are not available.

Use this status when a release should stay available for reference but no longer be changed.


Hawzu applies these rules in the status change window:

  • Not Started can’t be selected again once a release has been created. A new release starts as Not Started or In Progress.
  • Archived releases can’t move to another status.
  • Every other move is allowed. For example, a Completed release can be reopened to In Progress or Paused, or moved to Archived.

Moving a release to Completed or Archived freezes its readiness figures, and reopening it returns them to live. See Snapshot on completed or archived.


StatusExecution Behavior
Not StartedAllowed with warning
In ProgressAllowed
PausedBlocked
CompletedBlocked
ArchivedBlocked