---
title: "Commit Work (User Story Workflow)"
slug: "commit-work"
description: "Learn how developers commit completed work from a User Story to the Deployment Tower and save the associated changes."
updated: 2026-07-06T17:44:03Z
published: 2026-07-06T17:44:03Z
canonical: "documentation.decisions.com/commit-work"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Commit Work (User Story Workflow)

## Overview

This article demonstrates the third step of the Executing User Stories Workflow process: **Commit Work**. Once work has been completed on a User Story, Developers are able to save changes made to the Deployment Tower by committing the work. For more information about executing User Stories, please refer to [User Story Workflow (Developer Guide)](/v10/docs/user-story-workflow-developer-guide).

---

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Gemini_Generated_Image_xx2xexx2xexx2xex(3).png)

1. Once work has been completed, right-click the User Story and select **Commit Changes**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-07-06_09h42_34.png)
2. In the **Commit Changes** dialog:
  - Select the User Story.
  - Check whether the **User Story Is Ready For Review,** if applicable.User Story Is Ready For Review

    - This checkbox should be selected **only if the work is complete** and the developer intends for the story to be reviewed.
    - If there is still pending work and the developer simply wants to save progress to the deployment server, this checkbox can be left unchecked.
  - Add a commit message and click **Commit**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-07-06_09h43_38.png)