# Ticket-Based Change Management Ticket-based change management in Sprinto allows you to connect your organisation’s ticketing tools to track and verify all change requests automatically. By integrating supported systems, Sprinto collects change tickets as evidence, ensuring every modification follows your approved processes and meets compliance requirements. *** ### Supported Integrations Sprinto supports the following ticketing systems for change management tracking:
Ticketing SystemDescription
AsanaManage change requests using Asana projects.
ClickUpUse ClickUp folders and lists to log and monitor change requests.
HiveCapture actions and track progress within Hive projects.
Jira Service ManagementUse Jira Service projects to record and close change issues.
Jira SoftwareTrack change-related tasks within Jira Software projects.
LinearManage change stories within Linear projects.
ShortcutTrack stories across Shortcut projects for change evidence.
TeamworkCapture change tasks and completions within Teamwork.
TrelloTrack change cards and completions using Trello boards.
WrikeMonitor change-related tasks through Wrike projects.
Azure DevOpsTrack change requests and approvals using Azure DevOps projects and repositories.
FreshserviceTrack change requests and approvals using Freshservice change management.
*** ### How It Works Each integration connects Sprinto to your existing ticketing workflow. Once configured: * Sprinto fetches tickets from the specified project or board. * The system identifies open and closed change tickets based on your defined statuses. * Closed or completed tickets are automatically used as change management evidence. *** ### Set Up Ticket-Based Change Management Below are the setup and configuration guidelines for each supported tool. *** #### **Asana** **Setting up a change management project** 1. Create a dedicated project in Asana to manage change requests.\ Refer to [Asana’s project setup guide](https://asana.com/guide/help/projects/basics). 2. Ensure every task has an assignee different from the task creator. 3. Maintain clear task statuses such as *To Do*, *Doing*, and *Done*. 4. Mark completed tasks as *Done* or *Completed*. **Configuring Asana in Sprinto** 1. Locate your project ID from the URL, for example:\ `https://app.asana.com/0/1111094557386982/list` 2. Use this project ID when adding Asana as a change management system in Sprinto. 3. If you use custom sections, specify which section represents the *Completed* status. *** #### **ClickUp** **Setting up a change management project** 1. Create a dedicated folder (project) and list in ClickUp.\ Refer to [ClickUp’s folder and list guide](https://docs.clickup.com/en/articles/887681-learn-the-difference-between-folders-and-lists). 2. Ensure tasks are assigned to different users from their creators. 3. Use statuses such as *To Do* and *Complete*. 4. Always ensure the *Complete* status indicates task closure. **Configuring ClickUp in Sprinto** 1. Identify your list ID in the URL, for example:\ `https://app.clickup.com/37469628/v/l/li/187334481` 2. Use this list ID when connecting ClickUp to Sprinto. 3. If using custom statuses, specify which status represents *Completed*. *** #### **Hive** **Setting up a change management project** 1. Create a dedicated project in Hive for change tracking.\ Refer to [Hive’s project creation guide](https://help.hive.com/en/articles/457193-hive-projects). 2. Assign all actions to users other than the creators. 3. Use statuses such as *Unstarted*, *In Progress*, and *Completed*. 4. Ensure completed actions are correctly marked as *Completed*. **Configuring Hive in Sprinto** 1. Find your project ID in the URL, for example:\ `https://app.hive.com/workspace/...projectId=6QEdrC8uYRXWj86s3` 2. Use this project ID when connecting Hive in Sprinto. 3. If using non-default statuses, specify which status represents *Completed*. *** #### **Jira Service Management** **Setting up a change management project** 1. Create a dedicated Jira Service Management project.\ Refer to [Atlassian’s setup guide](https://www.atlassian.com/software/jira/service-management/product-guide/getting-started/quick-start-guide#1-set-up-and-customize-your-project). 2. Assign issues to users other than the reporters. 3. Use statuses such as *Open*, *Pending*, *Work in Progress*, and *Done*. 4. Ensure *Done* represents a closed change. **Configuring Jira Service Management in Sprinto** 1. Locate the project ID from the URL, for example:\ `https://mychangemgmt.atlassian.net/jira/servicedesk/projects/ITCHANGE` 2. Use this project ID when adding Jira Service Management to Sprinto. 3. Specify your *Done* status if using custom workflows. *** #### **Jira Software** **Setting up a change management project** 1. Create a new project in Jira Software for change tracking.\ Refer to [Jira Software’s project guide](https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/). 2. Assign issues to different users from their creators. 3. Use statuses such as *To Do*, *In Progress*, and *Done*. 4. Ensure all completed issues are moved to *Done*. **Configuring Jira Software in Sprinto** 1. Find your project ID from the URL, for example:\ `https://mychangemgmt.atlassian.net/jira/software/c/projects/SCM` 2. Use this project ID when integrating Jira Software with Sprinto. 3. Specify your *Done* status if using a custom workflow. *** #### **Linear** **Setting up a change management project** 1. Create a separate project in Linear to manage change issues.\ Refer to [Linear’s project creation guide](https://linear.app/docs/projects#create-projects). 2. Assign issues to users other than the creators. 3. Use clear statuses such as *In Progress* and *Completed*. **Configuring Linear in Sprinto** 1. Locate your project ID in the URL. 2. Use this project ID when connecting Linear in Sprinto. 3. Specify your *Completed* status if custom statuses are used. *** #### **Shortcut** **Setting up a change management project** 1. Create a project in Shortcut for tracking changes.\ Refer to [Shortcut’s guide](https://help.shortcut.com/hc/en-us/articles/205702359-What-are-Projects-). 2. Assign stories to different owners from their creators. 3. Use states such as *Unstarted*, *Started*, and *Done (Completed)*. **Configuring Shortcut in Sprinto** 1. Identify your project ID from the URL, for example:\ `https://app.shortcut.com/changemgmt/project/14` 2. Use this project ID when connecting Shortcut in Sprinto. 3. Specify your *Completed* state if different from default. *** #### **Teamwork** **Setting up a change management project** 1. Create a dedicated project in Teamwork for change requests.\ Refer to [Teamwork’s project creation guide](https://support.teamwork.com/projects/getting-started/adding-a-project). 2. Assign tasks to users other than the creators. 3. Use statuses such as *Incomplete* and *Complete*. **Configuring Teamwork in Sprinto** 1. Locate your project ID from the URL, for example:\ `https://company.teamwork.com/#/projects/604392` 2. Use this project ID when adding Teamwork to Sprinto. 3. Specify *Complete* as the closure status. *** #### **Trello** **Setting up a change management board** 1. Create a dedicated board in Trello for managing changes.\ Refer to [Trello’s board creation guide](https://support.atlassian.com/trello/docs/creating-a-new-board/). 2. Assign cards to members other than the creators. 3. Use lists or due-date completions to mark cards as *Done*. **Configuring Trello in Sprinto** 1. Locate your board link in the URL, for example:\ `https://trello.com/b/vnbkLXiF/` 2. Use this link when adding Trello to Sprinto. 3. Specify which list represents the *Completed* state. *** #### **Wrike** **Setting up a change management project** 1. Create a project in Wrike to manage change tasks.\ Refer to [Wrike’s project guide](https://help.wrike.com/hc/en-us/articles/1500005120581-Creating-Projects). 2. Assign tasks to different users. 3. Use statuses such as *New*, *In Progress*, *Completed*, *On Hold*, and *Cancelled*. 4. Ensure all completed tasks are marked as *Completed*. **Configuring Wrike in Sprinto** 1. Find your project ID in the URL, for example:\ `https://www.wrike.com/workspace.htm?acc=5574523#path=folder&id=908244731` 2. Use this ID when connecting Wrike in Sprinto. 3. Specify *Completed* as your closure status if using custom workflows. *** #### Azure DevOps **Setting up a change management project** 1. Create or identify an **Azure DevOps project** that will be used to track change-related work items, pull requests, and deployments.\ Refer to the Azure DevOps project setup [documentation](https://learn.microsoft.com/en-us/azure/devops/organizations/projects/create-project?view=azure-devops\&tabs=browser) if needed. 2. Ensure change-related activities (for example, code changes, approvals, or deployments) are consistently tracked using: * Work items (such as Change Requests or Tasks) * Pull Requests for code changes 3. Assign work items and pull requests to appropriate owners responsible for reviewing and approving changes. **Configuring Azure DevOps in Sprinto** 1. Identify the **organisation and project** you want to monitor in Azure DevOps. 2. Connect Azure DevOps in Sprinto using the required authentication details when prompted. 3. Select the repositories and branches to monitor for change management checks. 4. Ensure pull requests and branch policies (such as approvals and status checks) are enabled for the selected repositories. *** #### Freshservice **Setting up a change management project** 1. Use **Freshservice Change Management** to log and track change requests for your organisation.\ Refer to Freshservice [documentation](https://support.freshservice.com/support/solutions/articles/50000000655-get-started-with-change-management) on change management if required. 2. Ensure all changes are created and managed as **Change Requests** in Freshservice, with appropriate details such as risk, impact, and approval workflow. 3. Assign change requests to relevant owners and approvers responsible for reviewing and implementing the changes. 4. Use Freshservice change statuses (for example, *Open*, *In Progress*, *Pending Approval*, and *Completed*) to reflect the lifecycle of each change. *** **Configuring Freshservice in Sprinto** 1. Identify the **Freshservice account and workspace** that contains your change requests. 2. Connect Freshservice in Sprinto using the required authentication details. 3. Specify the change request types and statuses that Sprinto should consider as valid evidence for completed changes. 4. Ensure completed change requests accurately reflect approvals and closure to satisfy change management checks. Once configured, Sprinto continuously monitors Freshservice change requests and uses them as evidence for change management compliance. *** ### Best Practices * Create a **dedicated project or board** in your chosen tool exclusively for change management. * **Ensure segregation of duties** — the ticket creator and assignee should be different. * Clearly define and maintain **status workflows** for open and closed states. * Periodically review project mappings in Sprinto to ensure accurate tracking.