Azure DevOps is a platform from Microsoft that offers a DevOps tool for developing and deploying software. Install Azure DevOps extension in Zoho Sprints and accelerate the software development process.
Click the gear icon at the top-right. The settings window will appear.
Click Others under Marketplace section. The listing page will appear.
Click Configure under Azure DevOps .
Check the Terms and Conditions box and click Authorize.
You will be redirected to your Azure DevOps account. Enter your credentials and view the scopes the application has access to.
Accept the terms and conditions and the page will redirect to Zoho Sprints.
Projects in AzureDevOps will be listed under My Azure DevOps Projects . The projects mapped with the projects in Zoho Sprints will be listed under Team Azure DevOps Projects .
Choose the organization of the projects you'd like to associate with.
Hover and click the arrow to map repository with the workspace.
Click Associate Projects and choose the project to be mapped. If you would like to sync work items, click Sync only Bugs.
Click Associate.
Navigate to the details page of a work item in Zoho Sprints.
Select the Azure DevOps tab.
Click the + Commit button.
Select a mapped project.
Select a repository.
Filter commits by start and end date.
Select the commit.
Click the Attach button. The commit will be attached to the item.
To attach pull requests to an item:
Navigate to the details page of a work item in Zoho Sprints.
Select the Azure DevOps tab.
Select the Pull Request tab.
Click the + Pull Request button.
Select a mapped project.
Select a repository.
Filter status.
Select the pull request.
Click the Attach button. The pull request will be attached to the item.
Note:
You can also use these Quick commands to attach commits and pull requests from Azure DevOps.
Work item tagging is supported only through the pull request "Description" field.
Format | Syntax | Purpose |
#workitem | #<Project Prefix>- <i/I><Item number> Example: #SP-i30 | Represents the work item ID. |
#comment | #workitemid #comment <message1> #comment <message2> Example: #SP-I15 #comment Please share the final build by EOD. #comment Fix the existing issues and update the local build. Note: You can add multiple comments to a single work item. | Add comment for the work item. |
#status | #workitemid #status <status_name> Example 1: #SP-i20 #status Done Example 2: #SP-i20 #status To_be_Tested Note: 1. If the status name carries multiple words, separate them with an underscore. 2. Statuses are not case sensitive. | Update the status of the work item. |
#priority | #workitemid #priority <priority_name> Example 1: #SP-i40 #priority Critical Example 2: #SP-i42 #priority Should_be Note: 1. If the priority name carries multiple words, separate them with an underscore. 2. Priorities are not case sensitive. | Update the priority of the work item. |
#time | #workitemid #time <hours>h <minutes>m Example: #SP-I52 #time 5h 30m | Add log hours for the work item. |
Note: The email address of the Azure DevOps account should be registered with the Zoho Sprints team only then they can process the commits: #comment, #time, #status, and #priority.
Single command for multiple work items
Syntax | #workitemid,#workitemid,#workitemid #comment <message> |
Example | #SM-I25,#SM-I42,#SM-I98 #comment Issues are resolved and updated in the local build. |
What happens? | All the three work items are added with the comment. |
Multiple commands for single work item
Syntax | #workitemid #comment <message> #priority <priority_name> #time < > h < > m #status <status_name> |
Example | #SM-I34 #comment List out the requirements #priority High #time 5h 3m #status In_progress |
What happens? | The work item is added with comment and log hours. It is also updated with status and priority. |
Multiple commands for multiple work items
Syntax | #workitemid,#workitemid,#workitemid #comment <message> #priority <priority_name> #time <>h <>m #status <status_name> |
Example | #SM-I34, #SM-I45, #SM-I54 #comment List out the requirements #priority High #time 5h 3m #status In_progress |
What happens? | All the three work items are added with comments, log hours and updated with status and priority. |
Note:
You can attach commits and pull requests to a work item only if the Azure DevOps project is associated with the Zoho Sprints project of that work item.
The user should have permission in Azure DevOps profile to view the details page of a work item in Zoho Sprints.
All the work items added in the Azure DevOps account will be automatically be added to the Zoho Sprints Backlog. Fields such as Item Type, Status, Priority, Title, Tags and Description will remain the same if it matches with the data in Zoho Sprints.
Fields synced from Azure DevOps
Fields: Title, Description, Item Type
Note:
In Azure DevOps once you move the work item to trash, the sync with Zoho Sprints item stops.
The status of the work items depends upon the sprints they are a part of.
All the comments added/edited/deleted from your work items in Azure Devops will reflect in Zoho Sprints.
Similarly, when a work item is created in Sprints, the creation screen includes the option to add it to Azure DevOps. This enables you to add items to Azure DevOps from your Sprints account.
Fields synced from Sprints
Fields: Title, Description, and Item Type
Note:
Only the repositories with "Sync Only Bugs" enabled will be listed in the Create Item window.
Status of the work items will be mapped to the open and closed status in Azure DevOps.
Click the gear icon at the top-right. The settings window will appear.
Click Others under Marketplace section. The listing page will appear.
Select Azure DevOps.
View the Project(s) Associated.
Click Remove Project.
Click the gear icon at the top-right. The settings window will appear.
Click Others under Marketplace section. The listing page will appear.
Select Azure DevOps.
Click the arrow icon to move the repositories out of the workspace.
Click the gear icon at the top-right. The settings window will appear.
Click All under Marketplace section. The listing page will appear.
Find Azure DevOps for Zoho Sprints.
Click Uninstall. The extension will be uninstalled and configuration will be removed.
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.