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.

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 or Completed.

Use this status during active test execution.


The release is temporarily on hold.

  • Executions are blocked.
  • The release can move back to In Progress.
  • The release can also be marked Completed.

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 — reactivate the release by moving it back to In Progress (or Paused), or move it to Archived.

Use this status after testing is finished. Completed is not a locked state — 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:

  • Archived releases cannot move to another status.
  • Completed releases can move to any other status — for example, reactivate to In Progress, or move to Archived.
  • Not Started cannot be selected after a release has already moved to another status.

StatusExecution Behavior
Not StartedAllowed with warning
In ProgressAllowed
PausedBlocked
CompletedBlocked
ArchivedBlocked