Onboard Agile Development 2.0 to DevOps Change Velocity — Workspace

Connect to your Agile Development 2.0 instance using the DevOps Change Workspace playbook to enable tracking of stories and epics.

Before you begin

Complete the tasks specified in the Getting started with DevOps Change Velocity topic.

Activate the Agile Development 2.0 plugin. For more information, see .

Role required: sn_devops.admin or sn_devops.tool_owner

Procedure

1. Navigate to Workspaces > DevOps Change Workspace and use one of the following options to open the Playbook to onboard Agile Development 2.0.

   Option	Steps
   Homepage	Select Connect a tool. On the  Connect to a tool  modal, select Agile Development 2.0 from the Plan category.
   Applications module	Select Applications () from the primary navigation. Select an existing application, or create one. To create an application, see Create an application - Workspace. From the  Recommended actions  pane, select the  Connect a tool  card. On the  Connect to a tool  modal, select Agile Development 2.0 from the Plan category.
   Tools module	Select Tools () from the primary navigation. From the Capability list, select Planning. Select Connect a tool. On the  Connect to a tool  modal, select Agile Development 2.0.

   Important:

   If you want to discover and track tool objects like plans while connecting to the tool, you must connect your tool from the Application module.
2. In the Tool name field, enter a name for the tool.

   

3. Select Next.

   The DevOps playbook opens to help you complete the onboarding tasks.

4. Select Connect.

   

5. Specify the access for the tool.
   1. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.
      The tasks these users in the groups can perform depends on the role assigned to them.

      • DevOps Tool Owner role: Can view and edit the tool.
      • DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
      • DevOps Administrator role: Can edit all tools.
      • Other DevOps roles: Can view the tool.
      Note:

      If you don't select a group and skip this step, all users with the DevOps Tool Owner role will be able to edit the tool.
   2. If you choose to control access to the tool, the All App Owners can view and associate tool objects to applications option becomes available for selection.

      This option enables all users having the DevOps App Owner role to access the tool. If selected, they’ll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.

   3. Select Assign.

   

   Important:

   • If you're connecting from the Home page or Tools module, the connection is complete and you're taken to the Summary page.
   • If you're connecting from the Applications module, then plans available in your project are discovered. You can track and import historical data from them.
6. Select the plans for which you want to track updates and associate to the application, and select Next.

   If you don’t choose to select plans now, you can enable nightly polling later to fetch the data for any tracked plans by setting the Enable Polling system property to Yes.

   

7. If you want to import plan data, select the date range and select Submit.

   You can import up to 90 days of data.

8. From the Summary page, select View tool record to review the details of the connected instance and the plans discovered from it.

   

Result

You’ve successfully onboarded your Agile Development 2.0 tool to DevOps Change Velocity.