Sprinto Dashboard

Ticket_Based_Change_Management

TABLE OF CONTENTS

  • List of integrations for Ticket Based Change Management

  • Guidelines to setup Change Management using a ticketing system

      • Asana

      • Setting up a change management project in Asana:

      • Configuring Asana as the change management system in Sprinto:

    • ClickUp

      • Setting up a change management project in ClickUp:

      • Configuring ClickUp as the change management system in Sprinto:

    • Hive

      • Setting up a change management project in Hive:

      • Configuring Hive as the change management system in Sprinto:

    • Jira Service Manager

      • Setting up a change management project in Jira Service Manager:

      • Configuring Jira Service Manager as the change management system in Sprinto:

    • Jira Software

      • Setting up a change management project in Jira:

      • Configuring Jira as the change management system in Sprinto:

    • Linear

      • Setting up a change management project in Linear:

      • Configuring Linear as the change management system in Sprinto

    • Shortcut

      • Setting up a change management project in Shortcut:

      • Configuring Shortcut as the change management system in Sprinto:

    • Teamwork

      • Setting up a change management project in Teamwork:

      • Configuring Teamworks as the change management system in Sprinto:

    • Trello

      • Setting up a change management project in Trello:

      • Configuring Trello as the change management system in Sprinto

    • Wrike

      • Setting up a change management project in Wrike:

      • Configuring Wrike as the change management system in Sprinto:

List of integrations for Ticket Based Change Management

The following Ticketing systems can be integrated with Sprinto to monitor change management tickets.

  • Asana

  • ClickUp

  • Hive

  • Jira Service Management

  • Jira Software

  • Linear

  • Shortcut

  • Teamworks

  • Trello

  • Wrike

Guidelines to setup Change Management using a ticketing system

Asana

Setting up a change management project in Asana:

  1. Sprinto recommends that you create a separate Project within Asana to manage your change management requests. Follow this help guide to set up a new project in Asana:https://asana.com/guide/help/projects/basics

  2. All Tasks (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the tasks, ensure that a person is assigned to the task. Also ensure that the person creating the task and the assignees are different. This is an audit requirement.

  4. Ensure that the task has clearly defined statuses to know when a task is Open and Closed. While creating a project in Asana, by default three sections are created: “To do”, “Doing” and “Done”. The Done section corresponds to the closed or completed status of a task.

  5. Ensure that all tasks that are completed are moved to the Done section. In Asana you can also use the “Mark Complete” button to indicate if a task is completed.

Configuring Asana as the change management system in Sprinto:

  1. Identify the Project ID in Asana. The project ID can be found in the URL of the project on Asana. For example: https://app.asana.com/0/1111094557386982/list

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default sections of “To do”, “Doing” and “Done”, then you need to specify the section in Asana that indicates the completed status.

ClickUp

Setting up a change management project in ClickUp:

  1. Sprinto recommends that you create a separate Folder (Project) and List within ClickUp to manage your change management requests. Follow this help guide to set up a new folder in ClickUp: https://docs.clickup.com/en/articles/887681-learn-the-difference-between-folders-and-lists

  2. All Tasks (Tickets) created under this Folder will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the tasks, ensure that a person is assigned to the task. Also ensure that the person creating the task and the assignees are different. This is an audit requirement.

  4. Ensure that the task has clearly defined statuses to know when a task is Open and Closed. While creating a Folder in ClickUp, by default two statues are created: “To do” and “Complete”. The Complete status corresponds to the closed or completed status of a task.

  5. Ensure that all tasks that are completed reflect the correct status in ClickUp.

  6. You can also choose to add additional statuses to the ClickUp Folder. Just ensure that the “Complete” status is always the status that indicates a task is closed or completed.

Configuring ClickUp as the change management system in Sprinto:

  1. Identify the List ID in ClickUp. The list ID can be found in the URL of the list on ClickUp. For example in the belowURL the list ID is mentioned after the prefix /li/: https://app.clickup.com/37469628/v/l/li/187334481

  2. Use this List ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “To do”, and “Complete”, then you need to specify the status in ClickUp that indicates the completed status.

Hive

Setting up a change management project in Hive:

  1. Sprinto recommends that you create a separate Project within Hive to manage your change management requests. Follow this help guide to set up a new project in Hive: https://help.hive.com/en/articles/457193-hive-projects

  2. All actions (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the actions, ensure that a person is assigned to the action. Also ensure that the person creating the action and the assignees are different. This is an audit requirement.

  4. Ensure that the action has clearly defined statuses to know when an action is Open and Closed. Hive provides the following default statues: “Unstarted”, “In Progress” and “Completed”. The Completed status corresponds to the closed or completed status of an action.

  5. Ensure that all actions that are completed reflect the correct status in Hive.

Configuring Hive as the change management system in Sprinto:

  1. Identify the Project ID in Hive. The project ID can be found in the URL as a parameter projectId. For example in the below URL the project ID is: https://app.hive.com/workspace/3qBdgSLZQFQ6Ka2u2?projectId=6QEdrC8uYRXWj86s3

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “Unstarted”, “In Progress” and “Completed”, then you need to specify the status in Hive that indicates the completed status.

Jira Service Manager

Setting up a change management project in Jira Service Manager:

  1. Sprinto recommends that you create a separate Project within Jira Service Manager to manage your change management requests. Follow this help guide to set up a new project in Jira Service Manager: https://www.atlassian.com/software/jira/service-management/product-guide/getting-started/quick-start-guide#1-set-up-and-customize-your-project

  2. All Issues (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the issues, ensure that a person is assigned to the issue. Also ensure that the person creating the issue and the assignees are different. This is an audit requirement.

  4. Ensure that the issue has clearly defined statuses to know when an issue is Open and Closed. While creating a project in Jira Service Manager, by default four status are available: “Open”, “Pending”, “Work in Progress” and “Done”. The Done status corresponds to the closed or completed status of a task.

  5. Ensure that all tasks that are completed are moved to the Done status.

Configuring Jira Service Manager as the change management system in Sprinto:

  1. Identify the Project ID in Jira Service Manager. The project ID can be found in the URL of the project on Jira Service Manager. For example: https://mychangemgmt.atlassian.net/jira/servicedesk/projects/ITCHANGE

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “Open”, “Pending”, “Work in Progress” and “Done”, then you need to specify the status in Jira Service Manager that indicates the completed status.

Jira Software

Setting up a change management project in Jira:

  1. Sprinto recommends that you create a separate Project within Jira to manage your change management requests. Follow this help guide to set up a new project in Jira Software: https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/

  2. All Issues (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the issues, ensure that a person is assigned to the issue. Also ensure that the person creating the issue and the assignees are different. This is an audit requirement.

  4. Ensure that the issue has clearly defined statuses to know when an issue is Open and Closed. While creating a project in Jira, by default four status are available: “To Do”, “In Progress” and “Done”. The Done status corresponds to the closed or completed status of a task.

  5. Ensure that all tasks that are completed are moved to the Done status.

Configuring Jira as the change management system in Sprinto:

  1. Identify the Project ID in Jira. The project ID can be found in the URL of the project in Jira. For example: https://mychangemgmt.atlassian.net/jira/software/c/projects/SCM

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “To Do”, “In Progress” and “Done”, then you need to specify the status in Jira that indicates the completed status.

Linear

Setting up a change management project in Linear:

  1. Sprinto recommends that you create a separate Project within Linear to manage your change management requests https://linear.app/docs/projects#create-projects

  2. All issues (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the issues, ensure that a person is assigned to it. Also ensure that the person creating the issue and the assignees are different. This is an audit requirement.

  4. Ensure that the issue has clearly defined statuses to know when a story is Open and Closed. In Linear, some status are available by default while others can be created. The “Completed” corresponds to the closed or completed status of a task.

  5. Ensure that all issues that are completed are moved to the Completed status.

Configuring Linear as the change management system in Sprinto

  1. Identify the Project ID in Linear. In the URL you will find the Project ID as part of it.

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “Completed”, then you need to specify the status in Linear that indicates the completed status.

Shortcut

Setting up a change management project in Shortcut:

  1. Sprinto recommends that you create a separate Project within Shortcut to manage your change management requests. Follow this help guide to set up a new project in Shortcut: https://help.shortcut.com/hc/en-us/articles/205702359-What-are-Projects-

  2. All stories (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the stories, ensure that a person is assigned to the story. Also ensure that the person creating the story (requester) and the assignees (Owner) are different. This is an audit requirement.

  4. Ensure that the story has clearly defined statuses to know when a story is Open and Closed. While creating a project in Shortcut, by default three main state categories are available: “Unstarted”, “Started” and “Done”. The Done state has an option “Completed” corresponds to the closed or completed status of a story.

  5. Ensure that all stories that are completed are moved to the Done status.

Configuring Shortcut as the change management system in Sprinto:

  1. Identify the Project ID in Shortcut. The project ID can be found by navigating to the Projects menu and clicking on the project you created for change management. In the URL you will find the project id as shown below: For example: https://app.shortcut.com/changemgmt/project/14

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of “Unstarted”, “Started” and “Completed”, then you need to specify the status in Shortcut that indicates the completed status.

Teamwork

Setting up a change management project in Teamwork:

  1. Sprinto recommends that you create a separate Project within Teamwork to manage your change management requests. Follow this help guide to set up a new project in Teamwork: https://support.teamwork.com/projects/getting-started/adding-a-project

  2. All tasks (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the tasks, ensure that a person is assigned to the task. Also ensure that the person creating the task and the assignees are different. This is an audit requirement.

  4. Ensure that the task has clearly defined statuses to know when a task is Open and Closed. In Teamwork a task is either in Incomplete state or Complete state that correspond to the Open and Closed status.

  5. Ensure that all tasks that are completed are marked as Complete.

Configuring Teamworks as the change management system in Sprinto:

  1. Identify the Project ID in Teamworks. The project ID can be found in the URL after the /projects/ prefix as shown below: For example: https://company.teamwork.com/#/projects/604392

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. Mention the status of closed as “Complete” to let Sprinto know which status indicates the completed status.

Trello

Setting up a change management project in Trello:

  1. Sprinto recommends that you create a separate Board within Trello to manage your change management requests https://support.atlassian.com/trello/docs/creating-a-new-board/

  2. All cards (Tickets) created under this Board will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the cards, ensure that a person is assigned to the story. Also ensure that the person creating the card and the assignees (Members) are different. This is an audit requirement.

  4. Ensure that the story has clearly defined statuses to know when a story is Open and Closed. In Trello, adding due dates and then marking them done marks it as complete.

  5. Ensure that all stories that are completed are moved to the Done status.

Configuring Trello as the change management system in Sprinto

  1. Identify the Board link in Trello. The Board link can be found by navigating to board’s menu and clicking on “More”. In the URL you will find the Board ID as part of the URL shown below: For example: https://trello.com/b/**vnbkLXiF**/

  2. Use this Board Link while adding a new change management system in Sprinto.

  3. In case of Trello, you need to specify the status that indicates the completed status.

Wrike

Setting up a change management project in Wrike:

  1. Sprinto recommends that you create a separate Project within Wrike to manage your change management requests. Follow this help guide to set up a new project in Wrike: https://help.wrike.com/hc/en-us/articles/1500005120581-Creating-Projects

  2. All tasks (Tickets) created under this project will be picked up by Sprinto as evidence for ticket based change management.

  3. For each of the tasks, ensure that a person is assigned to the task. Also ensure that the person creating the task and the assignees are different. This is an audit requirement.

  4. Ensure that the task has clearly defined statuses to know when a task is Open and Closed. In Wrike, the following status are available by default: “New”, “In Progress”, “Completed”, “On Hold” and “Canceled”. The “Completed” corresponds to the closed or completed status of a task.

  5. Ensure that all stories that are closed are moved to the Completed status.

Configuring Wrike as the change management system in Sprinto:

  1. Identify the Project ID in Wrike. The project ID can be found in the URL as an id parameter as shown below: For example: https://www.wrike.com/workspace.htm?acc=5574523#path=folder&id=908244731

  2. Use this Project ID while adding a new change management system in Sprinto.

  3. If you are not using the default statuses of ““New”, “In Progress”, “Completed”, “On Hold” and “Canceled”, then you need to specify the status in Wrike that indicates the completed status.

PreviousSet_Up_Change_Management_Systems_On_SprintoNextVulnerabilities