Creating Your First Change Request with Sort
Sort Change Requests are workflows designed to manage manual database changes efficiently and transparently.
Managing database changes can be a tedious and error-prone process, especially when those changes are too important to automate. Sort provides a modern workflow for proposing, reviewing, and applying database changes, inspired by GitHub pull requests. With Sort Change Requests, you can suggest modifications, additions, or deletions to your database—all without impacting the data until the changes are reviewed and approved.
Let’s walk through how to create your first Change Request with Sort.
What Are Change Requests?
Change Requests in Sort are workflows designed to manage manual database changes efficiently and transparently. A single Change Request can:
Add new rows to a database
Delete rows from a database
Modify existing values in a database
All proposed changes are safely isolated until they are approved and applied, ensuring data integrity and compliance.
Steps to Create a Change Request
1. Navigate to the Database
Begin by navigating to the database where you want to propose a change. Sort provides an intuitive interface to help you manage and review your data.
2. Change Data as Easily as a Spreadsheet
Locate the data within the database table you would like to modify, change the values, add new rows, or delete rows.
3. Propose the Changes
Make your changes directly in the Sort UI. Once you’re done:
Click “Propose Changes”
Add a Title to your Change Request.
Congratulations! You’ve created your first Change Request. From here, you can:
Add a detailed Description for context.
Assign Reviewers to evaluate the Change Request.
Add Labels for categorization.
Mention any related Issues that this Change Request may resolve.
Database owners will receive an email notification about your Change Request, ensuring that it’s promptly reviewed.
Reviewing and Approving Change Requests
Once submitted, your Change Request will enter a "Review Required" state. Any database owner within your organization can:
Review the proposed changes.
Approve the Change Request.
Optionally defer application to a later maintenance window.
After approval, the changes can be applied to the database seamlessly. If any issues arise during application, Sort will automatically roll back the changes and provide a detailed timeline for troubleshooting.
Tips for Success
Permissions: Ensure that you have the necessary permissions to approve Change Requests. Owners within an org can approve Change Requests, members can create them.
Notifications: Use the description and Reviewer functionality to keep stakeholders informed.
Error Handling: If changes fail to apply, Sort’s rollback mechanism will provide detailed logs to help you resolve the issue.
Why Use Sort?
Sort simplifies the management of valuable, manually-updated data, offering:
Transparency: A full history of who made changes, when, and why.
Efficiency: Streamlined workflows reduce admin and engineering time.
Security: Granular access controls keep sensitive data safe.
Whether you’re managing customer data, product information, or operational datasets, Sort empowers your team to handle manual changes with ease and confidence.
Ready to try Sort? Schedule a demo and see how Sort can transform your data workflows.